Golang DDD Architecture

Use this skill to shape a Go service so it stays easy to change, test, and reason about as business logic grows.

Start Here

• Check whether the service is complex enough to justify the pattern.
• Keep the design smaller for simple CRUD or authentication flows where read and write shapes are mostly identical and business rules are thin.
• Use the full workflow when handlers keep growing if trees, models are reused across boundaries, or dependencies are hard to mock or untangle.

Workflow

1. Inventory entry points and use cases.

• Start from HTTP handlers, gRPC services, CLI commands, message consumers, and scheduled jobs.
• Rewrite the supported operations in business language before moving code around.