Designing, building, testing and deploying microservices
summary
Describes moving a large mainframe legacy (cost ~€1M/year, one client had a DB with 142,000 tables) to a microservice approach using Java, JSON/HTTP, JUnit/Mockito/Hamcrest, Selenium and Sonar; teams model bounded contexts and small domain models (often four core objects), make each component has its own database, and automate tests so a new component can build a new component in a day or two and the pipeline deploy every night. First production takes ~1.5 years; full test suite runs 1–1.5 hours.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 2:43The challenge of monoliths
- 6:49Evolution of architectures
- 10:14The microservices hype cycle
- 13:57Key benefits and concepts
- 18:57Architectural considerations
- 22:48Learning and implementation
- 25:43Bounded context and modeling
- 31:21API design and communication
- 35:06Automated testing strategy
- 38:20From projects to delivery
- 41:57Conclusion and final advice
related talks
48mThirty months of microservices
01h 01mMicroservices Gone Wrong
51mMicroservices and Microfrontends: Scaling, Learning, Growing
29mMoving from A and B to ~150 microservices, the journey and learnings
23mOn the road from Monolith to Micro
01h 03mMicroservices: Decomposing Applications for Testability and Deployability
32mSplitting the monolith
55mMigrate your company to microservices: a step by step tutorial