backend-architecture-planner

Plan backend architecture by translating product goals into domain boundaries, services, and data flows. This approach defines responsibility ownership, integration points, and observability to prevent ad-hoc architectures and ensure reliable operations across services.

Define domain boundaries by mapping product features to clear responsibility ownership and domain maps. This process guides team alignments and establishes clear production constraints for features requiring non-trivial business logic and cross-domain coordination.

Choose between modular monolith and service-oriented approaches by evaluating your specific production constraints and cross-domain coordination needs. This architecture planning process provides decision guidance with justification based on your feature's data flows and eventing requirements.

Design data flows and eventing by mapping out jobs, events, and failure handling strategies across your services. This ensures reliable operations and establishes clear integration points for features with non-trivial business logic.

You need a formal backend architecture plan when building features with non-trivial business logic, cross-domain coordination, and clear production constraints. It ensures domain maps, responsibilities, integration points, and observability requirements are explicitly defined.

Yes, this backend architecture planning approach specifically applies to features with non-trivial business logic and cross-domain coordination. It satisfies requirements for domain maps, responsibilities, jobs, events, integration points, and observability.