Microservices and Microfrontends: Scaling, Learning, Growing
summary
A legacy sales monolith of 900,000 lines of code and 9 TB of data becomes a parallel rebuild into microservices using Spring Boot and Vue, deployed on AWS with Kubernetes, GitLab CI, Terraform and brokered async via Kafka (AWS MSK); microfrontends use single-spa. Teams grow from ~20 to 100+, services reach ~70 deployment units and ~30 DBs per stage, producing ~2,200 MRs/month and ~45 deployments/month. Result: first new product ships within months, regular 3-month product delivery, much higher availability, higher operational cost but clearer cloud cost visibility via OpenCost.
AI-written summary · about
chapters (20)
- 0:00Introduction and welcome
- 1:53Insurance market challenges
- 4:41Monolith environment and limitations
- 9:50Monolith problems and growth issues
- 11:55Vision for microservices transformation
- 14:03Infrastructure and cloud migration
- 17:31DevOps and learning new tools
- 18:34Microservices architecture vision
- 21:03Backend design and integration
- 23:32Frontend challenges and modern UI
- 27:04Micro frontends and integration
- 28:52New environment key data
- 30:00Ensuring software quality
- 31:45Service ownership and team structure
- 33:31Cost management and cloud benefits
- 36:19Organization and team roles
- 39:34Key learnings and benefits
- 43:09Migration strategy and patterns
- 45:16Challenges and team culture
- 46:20Q&A session
related talks
27mBuilding Microfrontend Architecture for Scale with JS
45mDesigning, building, testing and deploying microservices
01h 01mMicroservices Gone Wrong
18mMicroservices Out In the Wild
24mMicrofrontends
29mMoving from A and B to ~150 microservices, the journey and learnings
35mMicro frontend Has Entered the Game
36mMicrofrontends: Scalability Savior or Unmanageable Maze?