Legacy Monolith to Microservices

on YouTube ↗35m

" summary

Company migrates a 2005-era monolith to an event-driven bus architecture to decouple verticals, using Python services, RabbitMQ, Mesosphere/Kronos, New Relic, ELK and a custom telemetry collector (Redis → Influx) for metrics and queue lag. Teams model bounded contexts and apply CQRS/read replicas for favorites to avoid distributed transactions and accept eventual consistency. Result: 3.5M monthly users, ~20 ads/min, and the property vertical stays up when the legacy monolith crashes, proving the approach works.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:37About Me
3. 11:06Guiding Principles
4. 12:16Low Coupling and High Cohesion
5. 16:27Cqrs Design Pattern
6. 24:46Infrastructure Monitoring

" related talks

• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 23mOn the road from Monolith to MicroChristoph Moser · WeAreDevelopers Conference Vienna 2016
• 30mMonolith-ifying perfectly good microservicesBrian Scalan · Rails World 2023
• 23mMicroservices in a MonolithJoop Lammerts · phpDay 2019
• 40mBreaking the Monolith! Decoupling a Legacy Monolithic ApplicationRodrigo Orofino · QCon São Paulo 2019
• 23mMicroservices within a MonolithJoop Lammerts · DevDays Europe 2019
• 57mSplitting Monolith Application to MicroservicesAndrei Shakirin · ApacheCon@Home 2021
• 27mScaling a Rails Monolith w/Event Driven MicroservicesMarko Anastasov · WindyCityRails 2016