Mastering Domain-Driven Design for Superior API Strategy
summary
Applies Domain-Driven Design to an insurance API landscape and shows a lightweight, three-layer pattern: domain gatekeeping layer, an abstract business layer, and an anti-corruption layer. Implements separate ACL APIs for policy and claims against the same system of record so no cross-contamination occurs, keeps gateway APIs minimal and unversioned, and uses per-project HTML docs to empower developer teams. Results claim higher reuse, faster time-to-market, simpler maintenance, and successful rollout within the company without major infrastructure replacement.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:48Understanding not knowledge
- 3:13When to use DDD
- 14:23Strategic and Technical Design
- 18:43Domain jargon
- 21:05Example
- 23:00Implementation
- 23:52Insurance example
- 28:29Claims vs Policy example
- 31:56Gatekeeping API
related talks
44mCrafting Great APIs with Domain-Driven Design
59mDomain-Driven Design - Where Rubber Meets the Road
21mUsing the Power of APIs and Domain Driven Design to Embrace AI [...]
48mDomain-Driven Design tactically and practically
55mDomain-Driven Design: back to the roots
42mHigh-Speed DDD (revisited)
38mAPI Mastery: from the Design to Development
40mAutomated Governance in Practice