enterprise-architecture-patterns

Name: enterprise-architecture-patterns
Availability: InStock
Author: pohlai88

Guide engineers in applying enterprise-architecture patterns across distributed systems.

Updated Apr 5, 2026

Search Tags:#architecture #microservices #ddd #patterns #cqrs #event-sourcing

Ready to run

npx skills add https://github.com/pohlai88/afenda-vite-react --skill enterprise-architecture-patterns-pohlai88

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enterprise-architecture-patterns
Source: https://github.com/pohlai88/afenda-vite-react/tree/main/.agents/skills/enterprise-architecture-patterns
Command: npx skills add https://github.com/pohlai88/afenda-vite-react --skill enterprise-architecture-patterns-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers in applying enterprise-architecture patterns across complex distributed systems.

Core Features & Use Cases

Comprehensive catalog of patterns: DDD, Event Sourcing, CQRS, Sagas, API Gateway, Service Mesh, and scalability strategies.
Practical guidance for strategic and tactical design, context mapping, projections, and read models.
Real-world scenario guidance for multi-tenant SaaS, migration of monoliths to microservices, and API integration patterns.

Quick Start

Review the Pattern Catalog and implement bounded contexts, event sourcing, and a basic CQRS read model in your next service design.

Frequently Asked Questions about enterprise-architecture-patterns

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

FAQPage Schema

How do I design robust domain boundaries in microservices?▼

To design robust domain boundaries in microservices, apply Domain-Driven Design (DDD) to define bounded contexts and use context mapping. This isolates domain logic and structures complex distributed systems for scalable service interactions.

What is the best way to handle distributed transactions across microservices?▼

The best way to handle distributed transactions across microservices is implementing the Saga pattern. Sagas coordinate sequences of local transactions with compensating actions, ensuring data consistency across services without relying on distributed locks or two-phase commits.

When should I use CQRS and event sourcing in my architecture?▼

Use CQRS and event sourcing when you need scalable read/write models and a complete audit trail of state changes. CQRS separates command and query responsibilities, while event sourcing persists state as a sequence of domain events, ideal for complex domain logic.

Can I use enterprise architecture patterns for multi-tenant SaaS applications?▼

Yes, you can apply enterprise architecture patterns for multi-tenant SaaS applications. These patterns provide specific guidance for multi-tenant architectures, addressing tenant isolation, API integration, and scalable data models tailored for SaaS environments.

How do I migrate a monolith to microservices without breaking existing functionality?▼

Migrate a monolith to microservices by using DDD context mapping to identify bounded contexts and extracting them into independent services. This pattern provides real-world guidance to incrementally decouple modules while maintaining API integration.

Do I need an API gateway and service mesh for a distributed system?▼

You need an API gateway and service mesh in distributed systems to manage external routing and internal east-west traffic. These patterns provide structured communication, observability, and resilience across microservices.