manutej/luxor-claude-marketplace/enterprise-architecture-patterns
Claude Code and agent skill by manutej/luxor-claude-marketplace
- community
Checking that the SKILL.md file is still in the repository.
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability
Install
npx vskill@latest install manutej/luxor-claude-marketplace/enterprise-architecture-patternsSKILL.md
Enterprise Architecture Patterns
A comprehensive skill for mastering enterprise architecture patterns, distributed systems design, and scalable application development. This skill covers strategic and tactical patterns for building robust, maintainable, and scalable enterprise systems.
When to Use This Skill
Use this skill when:
- Designing microservices architectures for distributed systems
- Implementing domain-driven design (DDD) in complex business domains
- Building event-driven architectures with event sourcing and CQRS
- Designing saga patterns for distributed transactions
- Implementing API gateways and service mesh architectures
- Scaling applications horizontally and vertically
- Building resilient systems with fault tolerance
- Migrating monoliths to microservices
- Designing multi-tenant SaaS architectures
- Implementing backend-for-frontend (BFF) patterns
- Building real-time systems with event streaming
- Architecting cloud-native applications
Core Architectural Concepts
System Design Fundamentals
Separation of Concerns Divide systems into distinct sections where each section addresses a separate concern, reducing coupling and increasing cohesion.
Modularity Design systems as collections of independent modules that can be developed, tested, and deployed separately.
Abstraction Hide complex implementation details behind simple interfaces, making systems easier to understand and modify.
Scalability Dimensions
- Horizontal scaling: Add more machines/instances
- Vertical scaling: Add more resources to existing machines
- Data scaling: Partition data across multiple stores
- Functional scaling: Decompose by business capability
Consistency Models
- Strong consistency: All nodes see the same data at the same time
- Eventual consistency: All nodes will eventually see the same data
- Causal consistency: Related operations see consistent state
- Read-your-writes consistency: Users see their own updates immediately
CAP Theorem In distributed systems, you can only guarantee two of three properties:
- Consistency: All nodes see the same data
- Availability: Every request receives a response
- Partition tolerance: System continues despite network failures
Distributed Computing Fallacies
- The network is reliable
- Latency is zero
- Bandwidth is infinite
- The network is secure
- Topology doesn't change
- There is one administrator
- Transport cost is zero
- The network is homogeneous
Domain-Driven Design (DDD)
Strategic Design Patterns
Bounded Context
A bounded context is an explicit boundary within which a domain model is consistent and valid. It defines the scope where particular terms, definitions, and rules apply.
Key Principles:
- Each bounded context has its own ubiquitous language
- Models within a context are consistent
- Cross-context integration requires translation
- Contexts align with business capabilities
Implementation:
Context Mapping Patterns:
- Shared Kernel: Two contexts share a subset of the domain model
- Use when: Teams are closely coordinated
- Risk: Changes affect multiple contexts
- Customer-Supplier: Downstream context depends on upstream
- Use when: Clear dependency direction exists
- Pattern: Upstream provides defined API
- Conformist: Downstream conforms to upstream model
- Use when: Upstream is external/unchangeable
- Pattern: Adapt to external API
- Anti-Corruption Layer: Translate between contexts
- Use when: Protecting from legacy or external systems
- Pattern: Adapter/facade to translate models
- Separate Ways: Contexts are completely independent
- Use when: No integration needed
- Pattern: Duplicate functionality if necessary
- Open Host Service: Well-defined protocol for integration
- Use when: Multiple consumers need access
- Pattern: REST API, GraphQL, gRPC
- Published Language: Shared, well-documented language
- Use when: Industry standards exist
- Pattern: XML schemas, JSON schemas, OpenAPI
Ubiquitous Language
A shared vocabulary between developers and domain experts used consistently in code, documentation, and conversations.
Building Ubiquitous Language:
Tactical Design Patterns
Entities
Objects with unique identity that persist over time, tracking continuity and lifecycle.
Characteristics:
- Unique identifier (ID)
- Mutable state
- Lifecycle (created, modified, deleted)
- Equality based on identity, not attributes
Implementation:
Value Objects
Immutable objects defined by their attributes rather than identity, representing descriptive aspects of the domain.
Characteristics:
- No unique identifier
- Immutable (cannot change state)
- Equality based on all attributes
- Often passed by value
- Can be shared safely
Implementation:
Aggregates
Clusters of entities and value objects with clear consistency boundaries, accessed through a single root entity.
Key Principles:
- One aggregate = one transaction boundary
- External references only to aggregate root
- Root enforces all invariants
- Small aggregates perform better
- Eventual consistency between aggregates
Design Rules:
- Model true invariants in consistency boundaries
- Design small aggregates
- Reference other aggregates by identity only
- Update other aggregates using eventual consistency
- Use repositories to retrieve aggregates
Implementation:
Domain Events
Events that represent something significant that happened in the domain, enabling loose coupling and eventual consistency.
Characteristics:
- Past tense naming (OrderPlaced, PaymentProcessed)
- Immutable
- Include all necessary information
- Timestamped
- Often include aggregate ID
Implementation:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/luxor-devops-suite/skills/enterprise-architecture-patterns/SKILL.md
Popularity
- Repository stars
- 54
- Repository forks
- 15
- 7-day trend score
- 20
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 1 May 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/manutej/luxor-claude-marketplace/enterprise-architecture-patterns)