From Chaos to Domain Driven Design in Go
summary
Applies Domain-Driven Design (DDD) to Go applications to organize messy code and avoid issues like cyclic dependencies. Covers strategic DDD (ubiquitous language, bounded contexts, shared kernel) and tactical DDD (entities, aggregates, value objects) with practical, code-focused examples and recommended structuring practices for Go projects.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:36WHO WE ARE (FOGO)
- 11:36PACKAGE ARCHITECTURE (CONTRAPRESTACIONES)
- 16:33HEXAGONAL ARCHITECTURE
- 23:25DRAWBACKS OF THIS ARCHITECTURE
- 24:59THE CONTEXTS OF OUR APPLICATION
- 25:52CONTEXTUALIZING OUR APPLICATION
- 29:26NEXT STEPS
- 30:44LINKS TO THE MATERIAL
- 32:59CONTEXTUALIZING OUR APPLICATION
related talks
47mDomain-Driven Design in Go — It Doesn't Hurt (Much)
44mGo in Domain Driven Design
49mExploring domain driven design in Go
34mWriting idiomatic Go using Domain Driven Design
29mRethinking Domain-Driven Design in Go
30mFrom Chaos to Domain Driven Design
38mWhat I talk about when I talk about Domain Driven design
50mGetting Started with Domain-Driven Design without Fighting the Wrong Battles
