Microservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
summary
A team replaces 14 tiny .NET microservices and RabbitMQ with a single modular monolith and in-process messaging using Mediator replacing RabbitMQ, running both side-by-side for a month while migrating messages one-by-one. Two databases become one SQL Server, Kubernetes and nested VMs get replaced by Ubuntu services, and a delivery cadence with Thursday code freezes, Friday physical bot walkthroughs and Monday/Tuesday production updates enables daily shipping. Result: 7% more picks per hour and releases jump from monthly to 30+ a month.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 1:58The distributed monolith problem
- 4:25Simplifying the architecture
- 6:56Results and improvements
- 8:07Key lessons learned
- 9:56Closing and Q&A
related talks
48mMicroMonolith
01h 01mMicroservices Gone Wrong
01h 03mMicroservices vs The Distributed Monolith
44mMicroservices - How to create problems by solving problems?
54mFrom a distributed monolith to a microservices solution
35mMicroservices: A Tale of 3 Heroes
23mOn the road from Monolith to Micro
36mMicroservices Lessons Learned