Maturity model for Microservices: Untangling a Big Ball of Mud
summary
Defines a maturity model for microservices aimed at resolving tangled, monolithic codebases (a ‘big ball of mud’). Covers practical criteria and stages for assessing and improving microservice architecture using industry practices and patterns familiar to teams building APIs with tools like Postman.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:10History of Microservices at Postman
- 2:45Dependency Hell
- 6:51Big Ball of Mud
- 7:21Domain Driven Design
- 9:16Teams
- 10:30Context Mapping
- 12:31Principles of Microservices Design
- 13:02SLAS across Bounded Contexts
- 14:10Maturity Model & Bounded Contexts
- 18:16Aggregate View
related talks
52mWhat Does a Good Microservice Architecture Look Like?
46mFrom microservices to migroservices
27mThe technical journey to microservices
52mI Have a Microservices Architecture and I Didn't Know.
44mPragmatic Microservices
51mResponsible Microservices
32mMicroservices: A retrospective
45mMicroservices: A retrospective