enterprise-architecture-patterns

Catalog enterprise architecture patterns for distributed systems.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Abdullahmohammadaref/acar --skill enterprise-architecture-patterns-abdullahmohammadaref
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-architecture-patterns
Source: https://github.com/Abdullahmohammadaref/acar/tree/main/.agents/skills/enterprise-architecture-patterns
Command: npx skills add https://github.com/Abdullahmohammadaref/acar --skill enterprise-architecture-patterns-abdullahmohammadaref

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and implementing scalable, maintainable distributed systems with consistent patterns is challenging; this catalog provides a comprehensive guide to enterprise architecture patterns.

Core Features & Use Cases

  • Comprehensive catalog of patterns spanning DDD (strategic and tactical), Event Sourcing, CQRS, Sagas, API gateway, service mesh, resilience, and scalability.
  • Practical guidance, decision frameworks, real-world examples, and governance considerations for multi-tenant and microservices contexts.
  • Hands-on templates and checklists to align architecture decisions with business goals and compliance requirements.

Quick Start

Review the catalog, select a pattern, and apply it to your project using the guidance provided.

Frequently Asked Questions about enterprise-architecture-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What enterprise architecture patterns are needed for designing scalable microservices?

Scalable microservices require enterprise architecture patterns like Domain-Driven Design, CQRS, Event Sourcing, and Sagas to manage distributed state and maintain service boundaries in distributed systems.

How do I apply DDD strategic and tactical patterns in a multi-tenant SaaS platform?

Applying DDD in multi-tenant SaaS involves using strategic patterns to define bounded contexts and tactical patterns to build domain models, guided by decision frameworks that align architecture decisions with business goals and compliance requirements.

When should I use event sourcing and CQRS in distributed systems?

Event sourcing and CQRS should be used in distributed systems when you need to audit state changes, decouple read and write workloads, or implement complex domain logic across microservices, supported by practical governance and implementation guidance.

Does this enterprise architecture catalog provide implementation guidance for service mesh and API gateways?

Yes, the catalog provides implementation guidance, decision frameworks, and real-world examples for service mesh and API gateway patterns to support governance and modernization in multi-service platforms.

What are the limitations of using Sagas for distributed transactions across microservices?

Limitations of Sagas for distributed transactions include managing complex compensating actions for failures and eventual consistency, requiring careful state coordination addressed by provided implementation checklists and governance frameworks.