A practical tale of assessing a Microservices Architecture
summary
Assessing a Fortune Global 500 event‑driven microservices system by mining source code, messaging graphs and interviews uncovers concrete failures: components with 19,000 lines of code, 65 event types including 65 event types some without producers or consumers, and data volumes of hundreds of GB of text. A DDD reference design is produced (initial 12+ bounded contexts reduced to 4 bounded contexts), revealing misplaced responsibilities, unversioned async APIs, at‑least‑once non‑idempotent processing, missing load limits and tracing, and a prioritized action plan that makes the current baseline reliable and the future design less granular.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:16Context and engagement scope
- 3:37System analysis methodology
- 7:22Initial assessment findings
- 8:34Structural deep dive
- 13:08Applying DDD for refinement
- 23:53Assessment summary
- 25:44Quality and operational review
- 29:35Action plan and roadmap
- 31:42Key takeaways
- 34:18Q&A session
related talks
36mA practical tale of assessing a Microservices Architecture
52mWhat Does a Good Microservice Architecture Look Like?
26mDrawing the right lines: DDD, APIs and Microservices
49mMicroservices guided by DDD and reactive systems paradigm
33mFrom Enterprise Architecture to Software Design - Critical Thinking
48mIT Architecture : All your micro-services are wrong PERIOD!
45mDesigning, building, testing and deploying microservices
37mStart with DDD when you have a monolith