Go in Domain Driven Design
summary
Covers applying Domain-Driven Design (DDD) to backend services written in Go, explaining why to use DDD, its advantages and drawbacks, and specific challenges encountered. Describes how to design internal service architecture in Go so it remains convenient and efficient to work with over time.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:29What is DDD
- 4:37Tactical design in Go
- 10:36Go project structure
- 13:05Domain types and aggregates
- 15:12Anemic domain model
- 15:55Domain services
- 18:44Application layer
- 21:52Dependency registry
- 23:18Presentation layer
- 24:29Final workflow
- 25:52Transaction handling
- 27:38Eventual consistency
- 28:21Book recommendations
- 28:42Summary
- 29:23Q&A
related talks
42mFrom Chaos to Domain Driven Design in Go
29mRethinking Domain-Driven Design in Go
49mExploring domain driven design in Go
49mHow to cook Domain Driven Design
34mWriting idiomatic Go using Domain Driven Design
38mWhat I talk about when I talk about Domain Driven design
59mDomain-Driven Design - Where Rubber Meets the Road
46mDomain Driven Design The Basics