go-ddd

An example of tactical domain-driven design.

The project is about to demonstrate a few points:

• internal/kit provides a comprehensive and abstracted API for publishing and subscribing domain events via Google Pub/Sub.
• An example of a general user account service having some RESTful API endpoints - sign up user and get user.
• An example of publishing and handling a domain event, to implement a requirement Send a welcome email to a user when the user signed up.
• The code design follows the principles of Clean Architecture(or Hexagonal architecture) focused in separating each concern of pure domain/business logic, non-functional requirements such as monitoring/logging/etc, and implementations of database/RPC/etc at a low infrastructure level.
  • For example, service.PasswordHashService at the application layer abstracts how it encrypts plain passwords in which algorithm. And the implementation, bcrypt.PasswordHashService, is at the port/adapter layer.
• Mocks and test suites are auto-generated code by mockery and go-suiteup tweaked from mockery by myself.

Test

go test ./...

Run

go run cmd/server/server.go

API examples

SignupUser

Path: /v1/users
Content-Type: application/json
Example request body:
{
	"email": "john@gmail.com",
	"password": "PASSWORD",
	"first_name": "John",
	"last_name": "Doe",
	"password": "asdf"
}
Example response body:
{
    "id": "SOME_RANDOM_UUID",
    "email": "john@gmail.com",
    "first_name": "John",
    "last_name": "Doe"
}

GetUser

Path: /v1/users/{user_id}
Example response body:
{
    "id": "SOME_RANDOM_UUID",
    "email": "john@gmail.com",
    "first_name": "John",
    "last_name": "Doe"
}