architecture-design

System architecture design involves analyzing requirements and constraints, then applying patterns like layered, microservices, CQRS, event-driven, or DDD. This generates architecture diagrams, component responsibilities, and ADR documentation following best-practice guidelines.

Choosing between microservices and DDD depends on your specific requirements and constraints. You can evaluate both patterns against your project needs using a structured design workflow that reviews decisions and outputs ADR records to justify the final selection.

You create ADR documentation by following a step-by-step design workflow from requirement analysis to decision review. This process uses ready-to-use ADR templates to record architecture decisions, ensuring component responsibilities and design rationale are clearly documented.

Yes, you can generate architecture diagrams and component tables for an e-commerce platform. The design workflow outputs ready-to-use templates for architecture overviews, component responsibilities, data storage selections, and deployment topologies tailored to your platform.

You should use CQRS or event-driven architecture when your system design requirements demand specific patterns for handling complex domain logic or high scalability. The design workflow evaluates your constraints to recommend the most appropriate pattern and generates supporting ADR documentation.