architecture-craft

What problem does it solve?

architecture-craft helps teams avoid costly architectural thrash by turning system design into a repeatable decision discipline grounded in trusted models, clear trade-offs, and explicit constraints.

Core Features & Use Cases

• Subdomain categorization (Core / Supporting / Generic) to allocate rigor and prevent reinventing solved problems.
• Bounded contexts + ubiquitous language to define consistency boundaries and reduce term confusion across teams.
• Architecture quantum + style selection to choose modular monolith vs distributed designs based on independent deployment, coupling, and data ownership.
• ADR-driven trade-off documentation so “why” decisions are preserved and re-litigations are avoided.
• Incremental decomposition (Strangler Fig + Sagas) to migrate safely without big-bang rewrites or incorrect distributed transactions.
• Inter-service communication rules + evolution guardrails such as tolerant readers and additive compatibility.

Quick Start

Use architecture-craft when you are planning a major system design or decomposition and need a clear bounded-context and ADR-based decision plan for how services and data ownership should work.