solution-architect

To design scalable architectures for distributed systems, you need structured guidance on pattern selection and trade-offs. This skill provides architectural recommendations using proven patterns like Saga, CQRS, and Event Sourcing to ensure maintainability and alignment across stakeholders.

Documenting architectural decisions is best achieved by creating Architecture Decision Records (ADRs). This skill enforces the creation of ADRs to capture rationales, recommended patterns, and trade-offs, ensuring execution teams and stakeholders stay aligned on cross-service interactions.

You need CQRS and Event Sourcing patterns when designing complex distributed systems that require strict data consistency and scalable cross-service data flows. This skill guides you on enforcing these patterns during technology evaluations and integration planning.

Yes, you can use this to plan cross-service integration and data flows across microservices or modular monoliths. It supports the production of architecture diagrams and rationales to map out interactions and align execution teams during architectural planning.

Generating a high-level architecture proposal for a new service involves selecting appropriate patterns and documenting ADRs. This skill helps you produce architecture artifacts, including decisions, diagrams, and scalability analyses to guide your technology evaluation.