The GoLang boilerplate that implements best practices for great foundation of event-sourcing Microservice with Kafka

• Run & Manage via CLI Command: Provides options to interact with golang application
• Makefile
• Live Reload
• Dependency Injection
• Configuration
• Health Check
• Database Migration
• Linter
• Docker & Docker Compose
• Logging
• Metrics Observability
• Unit Test
• End-to-End Test Sample

Decouples Golang web service to independent layers, the changes from one layer won't affect codes of the others.

• Application Layer
  • Controllers, Handlers
  • Command
  • Query
  • DTO (Mappers, Presenters)
  • Notifications
• Domain Layer
  • Entity, Aggregate
  • Value Object
  • Domain Event
• Infrastructure Layer (includes Persistence)
  • DB Models
  • Repository
  • Logging

A sample of clean architect for account bounded context, you can access to these codes with following path <root>/internal/account-sample. This is just for demonstration.

In many cases, service needs to handle real-time synchronous requests from client or other microservices to support application's user experience. With Request-Reply pattern, each service will send request and wait for response from other services via different channels, in this case are different Kafka topics

• https://en.wikipedia.org/wiki/Dependency_injection

The most obvious advantage of applying Dependency Injection pattern is decreased coupling between classes (structs) with their dependencies, your service will become testable with mocks, and easier to achieve high testing coverage

• Build CLI with Cobra: github.com/spf13/cobra
• Wire (Google): https://github.com/google/wire

• Enterprise Integration Patterns: Request-Reply