Golang DDD CQRS

Use this skill to split application logic into clear commands and queries without turning Go code into ceremony-heavy enterprise scaffolding.

Start Here

• Use CQRS when a service has meaningful write-side behavior, mixed read and write models, or application services that are hard to reason about.
• Skip or minimize CQRS when the service is mostly simple CRUD or login-like flows with little business behavior.

Workflow

1. Split the use cases into writes and reads.

• Commands mutate state and may return errors.
• Queries return data and should not perform business mutations.

2. Name them in business language.

• Prefer ScheduleTraining, CancelTraining, ApproveReschedule, AvailableHours.
• Avoid default CRUD names unless the business really speaks that way.