Challenges of distributed systems
summary
Recommendation is to start as a monolith and only migrate when growth makes changes slow and risky; migration requires three concrete stages—service decomposition, choosing synchronous vs asynchronous communication, and solving write consistency and read efficiency with patterns like saga pattern and CQRS. Operational tooling centers on containers and orchestration (Docker, Kubernetes) plus tracing via OpenTelemetry/Zipkin/OpenTracing. Migration is iterative (strangling the monolith), needs DDD to find bounded contexts, and costs significant engineering despite many frameworks.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:36Presentation summary
- 6:07Distributed systems vs microservices
- 10:14Deployments, data storage & comm. models
- 11:48Monolithic architecture - benefits
- 34:38Phases / stages
related talks
01h 07mChallenges of microservices Distribution Systems
42mQ&A - Monolith to Microservices
39mConsidering Migrating a Monolith to Microservices?
32mSplitting the monolith
31mMonolith to Microservices: A Guide to Seamless Transitions
48mMicroMonolith
43mMicroMonolith - Top anti-patterns of distributed systems
54mFrom a distributed monolith to a microservices solution
