Decomposing a monolith - engineering and operational strategies we have gleaned from our experience
summary
Practical strategies for breaking a legacy monolithic web application into microservices, with concrete lessons drawn from work at Endurance. Covers database migration and design decisions involving PostgreSQL, Cassandra and other NoSQL stores, plus operational topics like container orchestration and DevOps practices used to run the decomposed system.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:40About Endurance
- 1:14Our APAC Story
- 2:55Agenda
- 3:47Problems with Orderbox 1.0
- 7:29Micro-services to the rescue
- 9:50Sharing Database
- 10:41Duplication of Core capabilities
- 12:03Discover your first micro- service
- 14:48Modular Monolith
- 17:40Choose the right datastore
- 20:40Migrating traffic to the micro-service
- 22:15Monitoring the micro-service
- 25:02Improved scale with the first micro-service
- 26:00Centralised Authentication
- 29:10Issues with Bare Metal Deployments
- 30:52Containers & Orchestration
- 33:00Target state of Orderbox 2.0
- 34:54Takeaways
related talks
40mBreaking the Monolith! Decoupling a Legacy Monolithic Application
01h 03mFrom Monolith to Microservices: Story and Practice
01h 01mMonolith Decomposition Patterns
43mMonolith Carving
01h 52mMasterclass: Let's Cut the Monolith
32mSplitting the monolith
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
36mThe Art of Decomposing Monoliths