Integration Patterns for Microservices
summary
Compares concrete integration choices for microservices and when they fail: using a single shared database causes coupling across many small services, while event sourcing (example: a gaming leaderboard) stores event sequences to recompute scores reliably. Describes an OCR pipeline that scales workers via a messaging broker with publish–subscribe, and shows UI side-by-side composition combined with an API gateway for authentication and feature isolation, including architecture tradeoffs, implementation patterns, and real production examples.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 4:40Integration challenges in microservices
- 12:24Context mapping and boundaries
- 20:28Event-driven architecture basics
- 27:49Event sourcing and state management
- 34:12Deployment and scaling strategies
- 40:32Client-server interaction patterns
- 46:30Breaking monoliths into microservices
- 50:14Performance and caching techniques
- 55:07Security and authentication patterns
related talks
27mApplication Integration Patterns for Microservices
46mIntegration patterns & trade-offs for loosely coupled systems
24mPatterns of Evolution from Monolith to Microservices
46mGranularity & Communication for Microservices Architectures
30mApplication integration patterns for microservices
54m3 Patterns for Scalable Microservices
58mImplementing Event-driven Microservices
43mMicroMonolith - Top anti-patterns of distributed systems
