my-backend-architecture

What problem does it solve?

Organize and codify your personal backend architecture preferences into a clear, progressive disclosure model that guides layer boundaries and coupling rules.

Core Features & Use Cases

• Progressive layer rules: app / domain / infrastructure / shared as core four layers with an optional middle layer.
• Clear dependencies: one-way references, DIP direction, and explicit public API boundaries to prevent cross-layer leaks.
• Domain-first guidance: domain rules, aggregates, repositories, and test strategies organized across BCs.

Quick Start

Load the guidance and apply it to structure your backend project by defining four core layers and optionally a middle layer, then map code boundaries accordingly.