My favorite Go Backend architecture pattern

A Go developer with 3+ years of backend experience shares their preferred layered architecture pattern for Go projects. The pattern uses three layers — Handler (Controller), Service, and Repository — each backed by an interface and a single shared struct using Go's embedding feature. Code examples show how Gin is used for routing, GORM for database access, and how interfaces enable easy mocking for unit tests. A shared 'pkg' package pattern using functional options (InitialOption) is also demonstrated for reusable integrations. The post also honestly discusses a known limitation: handling database transactions that span business logic across Service and Repository layers is awkward compared to Spring Boot's @Transactional annotation.