Go Backend Structure

Purpose

This document explains why a standard Go backend is structured the way it is and what belongs where.

1. Core Principles (Remember These)

• Go has no framework-enforced structure
• Structure is a discipline
• Explicit > implicit
• One folder = one responsibility
• Entry points ≠ business logic

2. High-Level Folder Layout

api-go/
├── cmd/
│   └── server/
│       └── main.go
│
├── internal/
│   ├── routes/
│   ├── handlers/
│   ├── models/
│   ├── db/
│   └── middleware/
│
├── go.mod
└── go.sum

3. cmd/ — Runnable Applications

Purpose:

Contains all executable entry points.

Rules:

• Each folder inside cmd/ builds one binary
• Only startup logic lives here