Challenges of microservices Distribution Systems
summary
Covers why and when to break a monolith into independently deployable services, showing successful and hard cases: one trader middleware migration works, two marketing/market‑spread attempts struggle. Recommends Strangler pattern for incremental cuts, uses Saga pattern (1987) to keep distributed writes consistent, and runs services in containers (Docker, Kubernetes/OpenShift). Highlights real numbers (examples of 2.5M and 7M lines of code), Amazon’s ~12‑second deployment cadence as a goal, and core tradeoffs: data consistency, read performance, testing, monitoring and organizational alignment.
AI-written summary · about
chapters (16)
- 0:00Start
- 7:28Should We Migrate Our Project To Use Microservices
- 11:06The Differences between Distributed Systems and Microservices
- 23:21Challenges Organizational
- 24:14Scaling
- 30:06The Monolith versus the Micro Services
- 30:22Micro Services Architecture
- 31:46Independently Deployable Services
- 38:22Find the Boundaries of a Micro Service
- 40:22Saga Pattern
- 41:41Securing the Application
- 42:44Domain Driven Design
- 47:32Bounded Contexts
- 49:33Application Patterns
- 50:51Planning and Design
- 54:51Synchronous and Asynchronous Communication
related talks
01h 00mChallenges of distributed systems
24mPatterns of Evolution from Monolith to Microservices
43mMicroMonolith - Top anti-patterns of distributed systems
40mCAPtivating architecture: Navigating Distributed Systems and Microservices
46mGranularity & Communication for Microservices Architectures
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
51mScaling yout Architecture with Services and Events
54m3 Patterns for Scalable Microservices