Skip to main content

Backend Developer Guidelines (Go)

This section defines general engineering standards for Go backend services.

The goal is consistent architecture, predictable API behavior, safer data operations, and cleaner collaboration during development.

Rule Language​

  • MUST: mandatory rule
  • SHOULD: strong recommendation; deviations require clear rationale
  • MAY: optional pattern

Core Principles​

  1. Keep transport, business logic, and persistence concerns separated.
  2. Keep API contracts consistent and explicit.
  3. Keep data operations safe, bounded, and migration-driven.
  4. Keep code easy to review, test, and maintain.

Documentation Map​

  • Architecture: structure, layering, coding standards
  • API: routing conventions, status codes, validation, pagination, versioning
  • Infrastructure: database, migrations, caching
  • Operations: pull request checklist