Towards higher Reusability : Applying Clean Architecture to API Landscape.
summary
Applies Clean Architecture and Domain‑Driven Design to split a sprawling API estate into domain‑bounded layers with gatekeeping APIs and an anti‑corruption layer, so internal services change without forcing consumers to re‑test. Reports operating ~85 APIs with almost no regression testing after re‑layering, copies of problematic APIs instead of shared coupling, and a move to an agentic service mesh that lets agents and APIs orchestrate via an MCP and prompt engineering while keeping governance and TCO under control.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:53Clean architecture principles
- 7:07Hexagonal vs clean architectures
- 11:48Clean architecture at business level
- 18:08Domain driven design basics
- 20:38Domain boundaries design
- 24:50DDD key terms
- 27:39Layered API architecture
- 31:50Domain and anti-corruption layer
- 36:02Clean architecture benefits
- 36:24AI and agentic systems intro
- 41:45Clean architecture with AI
- 47:08Agentic AI six principles
- 51:02API-agent orchestration patterns
- 54:33AI API interaction examples
- 57:44AI challenges and mindset shifts
- 1:00:58Architect role and alignment
- 1:03:49Purity versus practicality
- 1:07:44Reverse pyramid engagement
related talks
28mHandling Legacy APIs with Domain Driven Design and Reactivity
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 02mImplementing the Clean Architecture in .NET Core
50mThe Grand Unified Theory of Clean Architecture and Test Pyramid
14mHow to build better and consistent APIs at scale
18mSoftware Architecture Building Better Applications with Architecture Best Practices
30mFrom futons to functions: the principles of good API design
01h 07mClean Architecture with .NET MAUI, Blazor, and ASP.NET Core