Changing the Game w/ Cloud, DevOps, & Microservices

Brian Chambers – Enterprise Architect

What to Expect from the Session

• Quick Intro• Share Chick-fil-A story• Dive into:

• Cloud• DevOps• Microservices

• Lessons Learned and Recommendations

• QA

Launch Week: June 1

Chick-fil-A Story - Where We Were

• Managed Data Center• Separate Development,

Ops, Testing, Architecture teams

• Lots of hand-offs• Monolithic architectures• Niche tools and

middleware platformsImage: public domain, credit http://en.wikipedia.org/wiki/Camel_Trail

Infrastructure

Cloud-Native vs. Cloud-Clumsy

Our Goals• Be able to respond to the business quickly• Availability / Scalability / Visibility / *ity

Our Approach:• Amazon Web Services• Use Higher-Order Platform Services

Supporting Cast of Services

Cloud-Native vs. Cloud-Clumsy

• Know the limitations of high-level services

• Security “IN” the cloud vs security “OF” the cloud

• “Lift-and-Shift” is a bad word

• Learn where/how to architect for HA

Cloud-Native vs. Cloud-Clumsy

Recommendations• Use higher order platform services• Strive for “serverless”• Win with security• Cover 80% of use cases with standard patterns• Focus a team on Foundation

Doing DevOps

DevOps?• Break down walls• Eliminate hand-offs• Empower developers

to build and create• Create right incentives• Build scalable delivery

model

Doing DevOps

Teams• “Pizza-sized” agile

teams• Self-Sufficient• Aligned with Products,

not ProjectsOps

• “You build it, you run it”

• Automate everything!• Start with CI / CD

Guilds• Center of Excellence• Share New Ideas

Tech• Narrow Tech Stack

• Cloud Platform Services + Microservices

• Spring + Java / Python

Doing DevOps

Key Takeaways• Make sure your teams are fully self-sufficient

• Business Analysts / Product Owners• Business Stakeholders• Lead / Architect• Developers• Testers

• Think Products, Not Projects• Have a bias towards getting to Production• Execute Agile in the way that works for each team

Defining Microservices

What is a “microservice”?• Do one thing and do it well• Deployed independently• Pieced together with other services to accomplish tasks• Per service choice of implementation language and

infrastructure• Easy to test and

understand

Microservices Keys to Success

Recommendations• Solve AuthN / AuthZ early - JWT is a winner!• Use a tool that gives you traceability & visibility (X-Ray)• Pick a good API Manager/Gateway• Pick a Registry/Portal (Swagger at least)

Wins and What’s Next

What’s Next?• More microservice-

based applications• All new development

in the cloud• Advanced Analytics• IoT• AI / Machine Learning

Wins• Customer Digital – CFA

One Mobile App• Restaurant Tax

Calculation• Restaurant Operator BI

App

Questions?

• Thank you!• Questions???

https://www.linkedin.com/in/brian-chambers-65960168/

Enterprise ArchitectChick-fil-A, Inc.

Where We Arrived

C l o u d P l a t f o r mS e r v i c e s

M i c r o -s e r v i c e s D e v O p s B u s i n e s s

A g i l i t y