game-backend-architecture-patterns

What problem does it solve?

This skill standardizes backend architecture for server-authoritative real-time games, enabling consistent behavior across the game server.

Core Features & Use Cases

• Modular Monolith First: A single deployable backend with clear internal module boundaries; MVP focuses on maintainability over microservices.
• Clean Architecture (Pragmatic): Domain → Application → Infrastructure layering; domain code remains framework-free and fully testable.
• Hexagonal Architecture (Ports & Adapters): Domain defines ports; infrastructure implements adapters; transport and persistence are treated as adapters.
• Domain-Driven Design (DDD – Pragmatic): Focus on aggregates, domain events, explicit invariants, and ubiquitous language to avoid over-modeling.

Quick Start

Analyze the current backend, split into domain, application, and infrastructure layers, and align modules and boundaries while introducing ports and adapters as needed.