Microservices from the trenches
summary
Rebuilds a VB6 time‑and‑attendance app as .NET Core microservices, using RabbitMQ for messaging, fan out exchanges initially then refactoring to topics after hitting 3000 messages per second; uses a JSON‑driven a slot API gateway for routing, header transformation and aggregation; teams run services on separate hosts so gateway and service discovery are needed; transactional messaging is not implemented; prototype works but complexity and organizational mismatch make microservices slower and heavier than a monolith would be.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:11Agenda
- 4:31Possible app architecture
- 5:38Services are...
- 8:42Benefits
- 9:57Drawbacks?
- 10:13The project
- 14:34Decomposing models
- 23:32Communication patterns
- 25:55Message broker concepts
- 33:26What should an API gateway do?
- 37:07Available options
- 43:33Conclusions
related talks
53mMicroservices from the Trenches. When Buzzwords Don't Make Your Application Work
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
57mUnderstanding Microservices: a guide for the monolithic developer
01h 01mMicroservices Gone Wrong
46mFrom Monolithic Monster to Majestic Microservice App
03mMicroServices - Let’s Build Some!
41m.NET Microservices in Real Life
54mHow one team built their first microservice