Evolutionary Architecture & Microservices
summary
Microservices break a monolith into small processes that communicate over lightweight protocols (often HTTP), own their separate databases, and are independently deployable so only the changed service needs redeploying. Design focuses on business capabilities, bounded contexts, and contract testing; expect frequent splitting and merging of service boundaries and plan for monitoring, infrastructure automation and continuous delivery. Strong DevOps culture is mandatory or operations will revolt — one project ended up with 11 XML parsing libraries before platform guardrails. Start with a monolith.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:22Componentbased reuse
- 1:09Serviceoriented architectures
- 6:24Microservices
- 7:27Microservices characteristics
- 10:28Implications of microservices
- 16:16Greenfield
- 22:23Evolutionary Architecture
- 28:27Continuous Delivery
- 31:08Getting Started
related talks
24mPatterns of Evolution from Monolith to Microservices
39mConsidering Migrating a Monolith to Microservices?
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
42mQ&A - Monolith to Microservices
01h 03mMicroservices: Decomposing Applications for Testability and Deployability
06mDo proper monoliths before you do microservices!
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
26mMicroservices