Migrating from a monolith to a new service
summary
Story of extracting moderator messaging from a monolith into a standalone microservice: the team moved data to a new database, rebuilt the small dashboard widget as an embeddable UI component and avoids CORS by routing browser requests through a monolith proxy that creates a JWT for the downstream service. Deployment happens with zero downtime, consistency is eventual via a configurable scheduled sync (typically 10-minute scheduled sync), multitenancy supports ~150 sites, outbox/event options considered but deferred for pragmatism.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:10Monolith and boundaries
- 3:58Domain driven design
- 6:27Service heuristics and Conway's law
- 14:37Strangler fig pattern
- 16:02First feature to migrate
- 20:31Micro frontend with embeddable UI
- 23:37Authentication and proxy integration
- 27:05Data sync challenges
- 33:23Eventual consistency and UX
- 36:08Future state and multi-tenancy
- 39:19Summary
related talks
57mMigrating from a monolith to a new service
01h 01mMigrating from a monolith to a new service
48mMicroMonolith
36mMicroservices Lessons Learned
42mQ&A - Monolith to Microservices
31mMonolith to Microservices: A Guide to Seamless Transitions
35mLegacy Monolith to Microservices
54mFrom a distributed monolith to a microservices solution