# evrone/go-clean-template

Clean Architecture template for Golang services

Repository: https://github.com/evrone/go-clean-template
Canonical: https://ross.abutalabs.com/products/go-clean-template
Language: Go
License: MIT
License Family: permissive
Topics: clean-architecture, go, golang, microservices, dependency-injection, template, example
Last push: 2026-08-25T02:04:30+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 100
- inputs: {"age_days": 2053, "days_push": 9, "days_rel": 11, "gap_med": 12, "n_releases_24m": 40}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 7659, forks 657 (observed 2026-08-28T04:10:02.230981+00:00)

## What it is
A copyable project template demonstrating how to structure Go microservices according to Clean Architecture (Uncle Bob) principles. It ships a working example service with REST (Fiber), gRPC, RabbitMQ AMQP, and NATS transports, plus PostgreSQL with migrations, Swagger docs, Prometheus metrics, OpenTelemetry tracing, and test setup.

## Use cases
- scaffold a golang microservice with clean architecture
- go project template for rest and grpc service
- learn how to organize business logic in a growing go service
- example of dependency injection in go
- boilerplate for go microservice with postgres and rabbitmq
- golang service skeleton with swagger and prometheus

## When to choose
- Starting a new Go microservice and wanting a proven, battle-tested project layout
- Learning how to layer domain, usecase, and transport code so a service stays maintainable as it grows
- You want a reference wiring of REST, gRPC, and message-broker RPC (RabbitMQ/NATS) with metrics and tracing included

## When to avoid
- You need a library or framework to import as a dependency — this is a scaffold you copy, not a package
- Small scripts or simple CRUD apps where a full layered architecture is unnecessary overhead
- Your team prefers picking its own stack (router, ORM, logger) and only wants architectural guidance rather than preselected tools

## Facets
- artifact type: learning-resource
- maturity: active
- function: boilerplate, developer-tools, microservices
- domain: backend, microservices, developer-tools, web-development
- platform: go, cross-platform
- tags: clean-architecture, project-template, boilerplate, golang, dependency-injection, scaffold, grpc, rest-api, fiber, rabbitmq, nats, postgresql, swagger, prometheus, opentelemetry, uncle-bob, docker

## Member repositories
- evrone/go-clean-template (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:02.230981+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:36:44.332094+00:00, confidence not recorded.
  - readme: https://github.com/evrone/go-clean-template (fetched 2026-08-28T04:10:02.230981+00:00, sha 7817d9d09ed5)
- Data as of 2026-08-30T08:39:29.467469+00:00.