Microservice Memoirs
Download as PPTX, PDF0 likes219 views
The document discusses the journey of a company called Lithium from using a private cloud with monolithic applications to adopting microservices on a cloud platform. It provides ground rules for implementing microservices including making sure to solve business problems first, embracing existing monoliths, and being incremental in the transition. Current practices at Lithium include using a common pipeline and platform with modular elements and migrating all new services to containers with container orchestration. Challenges that can arise with microservices are also acknowledged.
Microservice Memoirs
- 1. Microservice Memoirs @LachlanEvenson Team Lead, Cloud Platform Mike Ottinger Lead Full Stack Engineer
- 2. WHO ARE WE? The Lithium software platform helps brands connect, engage and understand their customers. 2
- 3. IT’S NOT JUST MICROSERVICES • Cloud • Automation • DevOps • Microservices • NoOps 3
- 4. CLOUD V1 • Private and Public Cloud – AWS – OpenStack • Lots of Forklifting • Waterfall 4
- 5. CLOUD V1 • Why weren’t we satisfied? 5
- 6. MIRCOSERVICES GROUND RULES • Make sure you are solving business problems • Service customer needs first • Embrace your monoliths • Control the tire fire • Be incremental • You will have to rethink everything 6
- 7. MIRCOSERVICES GROUND RULES CONT. • Create ambassadors • Stay in the “success zone” • Eat your own dog food • Make the running environment the current authority 7
- 8. THE CATALYST • Container revolution • Single artifact that is re-deployable • Kick the can approach - Incremental revolution 8
- 9. CURRENT STATE OF PLAY • Opinionated common pipeline and platform • Modular elements • All new services in containers • Container orchestration • New tooling 9
- 10. DEAD BODIES • Trouble in paradise – RPC – Circular dependencies – Maintaining consistent service contract points – Distributed tracing – Latencies 10
- 11. KEY TAKEAWAYS • Be incremental • Fail fast • Keep it simple • Opinion matters • Chase the MVP not perfection 11
- 12. THANKS! • Questions? We love questions! 12
- 13. Q & A WITH MIKE OTTINGER 13
Editor's Notes
- #2: Dialogue! Speaking from experience This is a reflection Platform perspective
- #3: Specifically, we build customer communities and social media monitoring tools for a ton of big brands like Virgin, Best Buy, Skype, AT&T and Autodesk.
- #4: The confluence of Cloud, DevOps and breaking down barriers Moving to a model where Dev not only managed writing off their app, but also the deployments
- #5: Critical problem – Not services customers Solving the problem operationally All your time is spent on infrastructure and not changing the App Dev experience
- #6: Devs found it harder to deploy applications It was easier to deploy to baremetal We’d changed the infrastructure but not the app deployment
- #7: Speaking from experience No one is green field
- #8: No one is green field
- #9: Focused on App Dev and provided means to quickly iterate Sequentially solving problems Disrupted ourselves. We’ve been hacking at docker for about a year. Are containers necessary, no but they helped
- #14: Have a customer share his microservice experience