Break Up the Monolith: Testing Microservices
summary
Argues that testability and explicit contracts decide microservice success and gives concrete practices: publish Swagger contracts and use tools like Shiva (GitHub) to generate tests from Swagger, version endpoints, use feature flags (toggles) and asynchronous queues (RabbitMQ) for nonblocking flows. Describes a rollout across 13 microservices, 150 developers with staged feature-flag scenes, multiple dry runs and rollbacks; outcome: 9 run-throughs, 200,000 logins/day, zero defects first week.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 5:56Rewrite or not to rewrite
- 7:22Evolution vs Revolution
- 9:10Release
- 10:05Microservices vs Monolith
- 13:09Testing Microservices
- 16:36API Contracts
- 18:49API Versions
- 20:14Feature Flags
- 22:00Asynchronous Processes
- 23:35Test Pyramid
- 24:38Development
- 28:14Data Generation
- 29:52Communication
- 31:45Definition of Done
- 32:31Example of Done
- 33:52We dont stay engaged
- 35:05GraphQL
- 35:15Before After
- 36:19The Plan
- 37:40Example
- 39:01What did we learn
- 41:14Pendulum not a gate
- 42:49Questions
related talks
43mBreak Up the Monolith: Testing Microservices
01h 03mMicroservices: Decomposing Applications for Testability and Deployability
08mTesting Microservices
14mMonolith 2 MicroServices Houston we've got a problem
27mThe technical journey to microservices
46mLove Your Monolith
57mEnd-to-End Automated Testing in a Microservices Architecture
45mBuilding a successful test automation architecture in a microservices environment