Microservices within a Monolith
summary
Describes how Procurios maintains a 15-year, 250k‑line monolith serving ~500k visitors with ~20 developers by using event sourcing and strict modular discipline to create independent, mutually unaware applications without splitting the repository. Concrete practices include isolating bounded contexts (user, ticket, registration), emitting domain events, integrating external services like Mailchimp, using Kafka for stream processing, and gradually extracting small services or bundles while keeping a single deployable codebase to preserve scale and reduce coupling.
AI-written summary · about
chapters (8)
- 0:00Microservices intro
- 3:33Monolith challenges
- 7:12User service
- 10:51Restructuring with services
- 15:28Ticket service
- 18:44Email notifications
- 20:13Migrating to microservices
- 21:20Summary
related talks
23mMicroservices in a Monolith
08mWhy we are writing a monolith, not a microservice
47mMicroservices? Monoliths? An Annoying Discussion!
35mLegacy Monolith to Microservices
48mMicroMonolith
43mMicroMonolith - Top anti-patterns of distributed systems
48mMicroservices vs The Distributed Monolith
57mSplitting Monolith Application to Microservices