architecture-patterns

Translate functionality requirements into architecture patterns by mapping user and admin flows to system contexts, containers, and components. Document inputs, outputs, dependencies, and error handling for each flow, then align architectural decisions with functional needs using a C4-inspired approach to prevent misaligned designs.

Design system architecture by first understanding existing architecture and functional requirements, then mapping flows to components and defining dependencies. Use System Context, Container, and Component views to visualize relationships, document trade-offs for each architectural decision, and ensure the design meets both performance and integration constraints.

Map user flows to architecture components by documenting user, admin, system, and integration flows end-to-end. For each flow, identify inputs, outputs, and dependencies, then assign them to specific containers and components. This ensures functionality is directly supported by your architectural design with clear visibility into error handling and integration points.

Use a C4 model when designing systems where understanding existing architecture and functionality requirements upfront prevents costly reworks. It's essential for complex systems with multiple integration points, APIs, or data models where System Context, Container, and Component views clarify how flows map to architecture across different stakeholder perspectives.

Functionality-first architecture designs systems purpose-built to support specific user and admin flows rather than applying generic patterns. It prioritizes mapping actual requirements to components with documented trade-offs, ensuring architectural decisions directly serve the system's intended functionality and constraints.

Document architecture decisions by outlining available options, listing pros and cons for each, and capturing consequences of your choice. This structured approach ensures decisions connect explicitly to functional requirements and integration considerations, creating a record of why specific architecture patterns were selected over alternatives.