Panel Session: Real World Boot-Up Sequences

Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a

Creative Commons Attribution-NonCommercial l icense: http://creativecommons.org/licenses/by-nc/3.0/

Real-World Boot-Up Sequences:

QuickBooks Self-Employed

By Tim Hobson – Engineer @

About Me

• Software Developer with a bad habit of leveraging frameworks

• Not a fan of re-inventing wheels every project

• Still believe you can move fast with good architecture

2

so old

About Our Product

3

Providing financial management

and compliance solutions for the

Self-Employed in the US and

(soon) globally.

Launched this year and

continuously releasing new

functionality.

very new

Context – In the Beginning…

New to the world offering, evolving product features

Be ready to pivot, pivot, and

pivot again

4

very ambitious

0 customers, aspirations

of millions

0 lines of code

Aggressive timeline for

initial release

Proven scale-ability,

extensibility required

No legacy, but need to

establish patterns early

Dev/Ops Productivity

essential

My Requirements

5

such needs

Powerful AND Simple?

6

?so

inconceivable

Tell us about your experiences with Spring Boot?

• No XML Config? No web.xml?

• Started prototyping with v0.5

• Bugs found, worked around

them

• Engaged with Spring Team

• Saw continual improvement

• …

7

such promise

Growing Pains

• WAR-based deployment

• myBatis Spring

• Understanding magic (Source debugging)

• @Conditional* …

• Cost-benefit analysis of defying convention

• Security customizations

• Web Sockets through multiple routers, apache httpd

8

concern

Tell us about your experiences with Spring Boot?

Cont’d

• Decided to adopt and GO

• Great Success!

• In production since May

• Rolling out new features every few

weeks

• Just released mobile companion

apps

9

amaze

Observations on what made it work

• Sample apps, documentation

• Enthusiasm, Evangelism and Direction from the Spring team

• Accessible source code with tests you can run!

• Developer inclusion in the process – ideas, contributions, fixes

• Truly no xml configuration – ever, as promised

• Massively simplified POMs

• Developer productivity

• Magic

• I would take this framework with me…

10

wow

On The Shoulders of Giants…

• General– @EnableAutoConfiguration– @EnableConfigurationProperties– YAML Configuration & Profiles

– “Starter” Dependency Management

– Boot Actuator

– ResourceBundleMessageSource– @Aspect– @EnableAspectJAutoProxy– @EnableTransactionManagement– @PersistenceContext– @EnableJpaRepositories– @Async– @EnableAsync

• Web– @EnableMvcSecurity– @EnableWebMvcSecurity– @EnableWebSocketMessageBroker– @ControllerAdvice– @ModelAttribute– @ExceptionHandler– SpringBootServletInitializer

• Batch– CRaSH ssh

– @EnableBatchProcessing– @EnableScheduling– @Scheduled– @Job

11

so enabled

What we configured/overrode/extended/built

• General• Data Migration (flywaydb)

• JpaVendorAdapter & EntityManagerFactory

• Batch• Always-on Batch process with @Scheduled

jobs

• On-demand batch job execution using CRaSH groovy commands

• Security• CSRF support for AngularJS

(HttpSessionCsrfTokenRepository)

• Custom Identity/Auth provider for Spring Security

• Hybrid Thymeleaf + Angular UI

• REST Authentication/Authorization

• Session Expiry, Authentication Failure, AccessDenied Handler

• Web• Container Customization (error pages)

• Unsupported Browser handling

• JS Min/SASS Build integration for Maven (exec-maven) calling compass and uglify

• Static asset versioning (git.properties)

12

such customize

Dev/Ops

• Actuator security

• Custom HealthIndicator• Custom Admin web console (leveraging Actuator

APIs, custom health checks) for ops and customer support

• SLF4J Logging with Logback and Splunk-friendly output

• Server-side error logging for Angular client

• On-demand user-level debug logging

• Memcache session storage to support automated rolling deployments

13

very sudo

Testing – Mocks and “System” Testing

14

@EnableAutoConfiguration@Profile("test")

@Beanpublic DataSource dataSource() {

return new EmbeddedDatabaseBuilder().setType(H2).build();}

@ActiveProfiles("test")@WebAppConfiguration@SpringApplicationConfiguration(classes={ApplicationConfig.class, TestConfig.class})…

public class UserControllerTest extends AbstractTestNGSpringContextTests {

private MockMvc mvc;

@BeforeClasspublic void setUp() {this.mvc = MockMvcBuilders.webAppContextSetup(this.context).build();

}

@Mockprivate Authentication authentication;…@BeforeTestpublic void setUp() {

MockitoAnnotations.initMocks(this);}

such ease

What’s Next?

15

Reactor

AMQP (RabbitMQ)

spring-session

Spring IO

Thanks!

Questions?

16

@hoserdude

@hoserdude

@hoserdude

hoserdude.com

Unless o therwise indicated, these slides are © 2013 -2014 Pivo tal So f tware, Inc. and licensed under a

Creative Commons Attribution-NonCommercial license: http://creativecommons.o rg/licenses/by -nc/3.0/



Porting legacy apps to Spring Boot in one week

By Erdem Günay (@gunayus)



About Turkcell

2



About Turkcell

3



How I met Spring Boot?

4



Turkcell Video – legacy BaaS

5



Turkcell Video – legacy BaaS

6



Porting to Spring Boot – end of 1st hour

7

http://spring.io/guides/gs/actuator-service/


Creative Commons Attribution-NonCommercial license: http://creativecommons.o rg/licenses/by -nc/3.0/ 8

Porting to Spring Boot – end of 1st day



Porting to Spring Boot – end of 1st day



Porting to Spring Boot – end of the week

• All the legacy REST APIs are migrated to @RestController(s)

• Architecture is redesigned

• Reimplemented as true, simple Spring 4 web application

• Zero mobile client update

• Faster development, running & debugging

• Jboss netty Apache web server & Tomcat 7

10



Porting to Spring Boot – number of sessions

%100



Porting to Spring Boot – throughput

12

0

50

100

150

200

250

300

350

400

450

500

Throughput (GB)

Total



Android Remote App Configuration







[operation] == 'command' and [manufacturer] == ‘turkcell' and [model] == 't50‘

{

"operation": "command",

"manufacturer": "turkcell",

"model": "t50", "appVersion": "31",

"board": "MSM8226",

"device": "msm8226",

"hardware": "qcom",

"networkCountryIso": "tr",

"resolution": "720x1184"

}

15



Ongoing projects

• All new projects are "bootiful"

• Object storage project with 1 Million users and 2 PB storage

capacity

• Mobile analytics platform 90 Million transactions per day

16

Spring

Framework

Spring

Security

Spring

Data

Spring

Integration

Spring

Social

Spring REST &

Web Services

Spring

Boot



Thanks

17

@gunayus

Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/

REAL WORLD BOOT-UP SEQUENCESBy Zach Lendon

@zachlendon


2

How a Journey to Spring Boot is helping save our enterprise brownfield

2

How a Journey to Spring Boot is helping save our enterprise brownfield


Code examples/links/slides

3

https://github.com/zachlendon/SpringOne2GX-2014 Or - contact me! More details/help available

https://github.com/zachlendon/SpringOne2GX-2014


Requisite Josh Long (@starbuxman) Quote

4


5

“Any application of sufficient complexity eventually sprouts a REST API”

- Josh Long, Building ‘Bootiful’ Applications with Spring Boot


6

“We need a ‘RESTful’ API”

• Large Spring Framework “Web Application” used for nearly all facets of hotel-related functionality you can do online

• However, rise in non-web applications, specifically mobile, required a new way to access functionality built into the existing web application


7

Enterprise Projects have “unique” constraints

• Re-use large, diverse set of existing ‘Spring’ services wherever possible, many of which are wired using - dare I say it - XML.

• Use JAX-RS • Re-use existing JAXB definitions, custom marshallers,

validators, etc • Any architectural changes in direction need to be gradual • Approachable technology solutions for a diverse team with

varying skill-sets, OS’s, etc.


8

Some Software Architecture Goals

• Standardize on, by using and/or extend, “best-of-breed” solutions around ancillary API functionality (logging, metrics, etc.) where possible instead of “home-grown” solutions

• Continue to support present-day devops and management comfort with WAR deployment while changing underlying structure to support future-day potential microservice-based dynamic build and deployment options

• Simplify • Provide Efficient, quality test coverage


Project Technology Implementation

9


10

Key Software Technologies Introduced / Explored

Technologies WhyGradle Build flexibility

Groovy / Spock Test Efficiency

Spring + Jersey Known core technology foundation Ultimate flexibility in adding future “pieces”

Still have flexibility to use Dropwizard

dropwizard-spring (hmsonline) Clean Dropwizard + Spring integration

Spring BootKnown, opinionated, simpler core tech foundation

Ultimate flexibility in adding future “pieces” Dropwizard similarities yet more


11

Spring + Jersey

• Configure Jersey ResourceConfig • Register your Jersey JAX-RS resources • Register RequestContextFilter • Register other Jersey Components

• Configure JerseyServlet • @Configuration or web.xml

• Setup Jersey JAX-RS Resources • Bean dependencies

• @Component and auto-wiring (@Autowire) • JSR-330 and @Inject


12

Spring + Jersey : Technical Thoughts : Pros/Cons

• Register your own custom Jersey ObjectMapper to provide data serialization/deserialization hooks

• Spring and Jersey are Best-of-breed solutions that technically fit together nicely and easily

• Developer-friendly and test-friendly • A production-tested solution around for several years

• Not an opinionated or full-stack solution = pro and con • Lack of out-of-the-box related features to easily leverage

• Not lightweight (WAR only) • not micro-service ready


13

Dropwizard-Spring

• Open-sourced by Health Market Science (https://github.com/hmsonline/dropwizard-spring)

• Can configure Jersey resources as Spring @Component • Can configure your Dropwizard components entirely with Spring

through YAML configuration file • Can extend project’s SpringService to hook into Spring /

Dropwizard “marrying” to add/modify behavior

https://github.com/hmsonline/dropwizard-spring


14

Dropwizard-Spring : Technical Thoughts : Pros/Cons

• Use Gradle • Gradle Shadow over Maven Shadow

• Use swagger-jaxrs-groovydoclet for creating Swagger artifacts from Groovy doc

• JAR only deployment (out of box) • Combining potential enterprise leeriness around Dropwizard with

a custom solution to tie it with existing Spring infrastructure


15

Spring Boot + Jersey

• Manual or use Jersey auto configuration from https://github.com/dsyer/spring-boot-jersey

• Auto-configuration allows Spring Boot to find JerseyConfig @Component and setup Jersey for you

• Spring-boot-actuator provides management and monitoring features similar to features Dropwizard surrounds Jersey with

• @AopAutoConfiguration can simplify your AOP/AspectJ mess • Embedded Servlet container (for JAR) vs still supporting WAR

deployment • Groovy & Spock friendly

https://github.com/dsyer/spring-boot-jersey


16

Spring Boot : Technical Thoughts : Pros/Cons

• Integration of Best of Breed Technologies (Spring, Jersey) with strong up-and-coming candidate in Spring Boot, from a known entity already in many enterprises

• Deploy as JAR or WAR huge for enterprise devops • Opinionated app foundation helps:

• set repeatable patterns for how to approach build-out of API and related services

• wrangle dependency tree, ease configuration overload/meltdown, lessen upgrade burden pain


17

Conclusion

• Lots of options for creating RESTful services with Spring, even when limited to specific technology choices (for better or worse)

• Spring Boot’s use cases are many • Help developers with app infrastructure and ancillary services so

that they can have best tools available at their disposal for building custom solutions

• Not just for greenfield - Spring Boot can be your gateway drug to a more modular/micro-service future for your brownfield application(s) as well

• Don’t be afraid to create your own Spring Boot configured components for maintainability of your project and use by other projects at your company (or by community if possible!)

Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ 18

Learn More. Stay Connected

Spring Boot is not just for greenfield! Don’t be afraid to gradually introduce in

existing apps big and small

Micro Service Architecture with Spring Boot and Groovy

Thurs, 8:30 with Marco Vermeulen

@springcentral | spring.io/video