enterprise-architecture-patterns

Model scalable enterprise architectures using DDD, event sourcing, CQRS, and saga patterns.

18|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/simnova/sharethrift --skill enterprise-architecture-patterns-simnova
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-architecture-patterns
Source: https://github.com/simnova/sharethrift/tree/main/.agents/skills/enterprise-architecture-patterns
Command: npx skills add https://github.com/simnova/sharethrift --skill enterprise-architecture-patterns-simnova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software architects and engineers design, evaluate, and implement robust patterns for large, distributed systems by combining domain-driven design (DDD), event sourcing, CQRS, saga coordination, and modern scalability practices.

Core Features & Use Cases

  • Design guidance for bounded contexts, aggregates, and ubiquitous language across complex domains.
  • Practical patterns for event streams, projections, and read models to support responsive interfaces and analytics.
  • Use Case: Architect a multi-tenant SaaS platform with clear data ownership, resilience, and scalable deployment.

Quick Start

Outline your system's core domains, map them to bounded contexts, and propose a pattern plan using DDD, event sourcing, CQRS, and saga for a multi-tenant architecture.

Frequently Asked Questions about enterprise-architecture-patterns

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

FAQPage Schema
How do I model bounded contexts and aggregates using domain-driven design?

Domain-driven design modeling defines bounded contexts and aggregates by mapping core domains to establish ubiquitous language and clear data ownership. This approach structures complex business domains into resilient, scalable multi-context architectures.

When do I need event sourcing and CQRS for scalable architecture?

Event sourcing and CQRS are needed for scalable architecture when supporting resilient event-driven projections and read models. They enable responsive interfaces and analytics by separating write operations from optimized query paths.

What's the best way to coordinate distributed transactions across microservices?

The saga pattern coordinates distributed transactions across microservices by managing sequences of local operations with compensating actions. It ensures data consistency without distributed locks across bounded contexts.

Can I use these enterprise architecture patterns for a multi-tenant SaaS platform?

These enterprise architecture patterns apply directly to multi-tenant SaaS platforms, providing clear data ownership, resilience, and scalable deployment. DDD, event sourcing, CQRS, and saga patterns combine to ensure robust multi-tenant isolation.

How do I design API gateway and service mesh patterns for event-driven systems?

API gateway and service mesh patterns for event-driven systems are designed by applying scalable enterprise architecture principles. They manage routing, resilience, and inter-service communication across distributed bounded contexts.

What are the limitations of applying saga and event sourcing to complex domains?

Saga and event sourcing introduce eventual consistency complexity and require careful read-model projection management. Governance documentation and structured pattern selection are essential to mitigate operational overhead in complex domains.