📎 Webclip
Implementing Domain-Driven Design with Go (2)
The article introduces part 2 of a series on Domain-Driven Design and Hexagonal Architecture with Go. It focuses on how the author implements tactical DDD patterns in the domain layer and says the choices shown are specific to the playground project.
Reading notes#
- The target audience is people interested in Domain-Driven Design and Go at any knowledge level.
- The author says they will point out where they deviate from idiomatic Go or do things differently than in usual Go projects.
- They treat higher-level concepts such as Domain-Driven Design and Hexagonal Architecture as stronger concerns than how most people implement things in a programming language.
- They still try to balance both concerns and find a good compromise where possible.
- They also plan to describe simpler alternatives when applicable.
- The author warns that readers who are strongly committed to idiomatic Go and are not interested in different ways of doing things, especially extra defensive code and separation between domain and infrastructure, may not find the series useful.
- The solutions presented are described as decisions made for the implementation of the playground project and not as a general prescription.
