Can it help me decide between microservices and monoliths?

Yes, it provides strategic guidance on defining bounded contexts and evaluating whether a modular monolith or microservices architecture better fits your team size and domain.

When should I use this DDD skill?

Use this skill when building complex systems with intricate business rules that require close alignment between software implementation and domain expertise.

Does it support tactical DDD patterns?

Absolutely. It offers specific implementation patterns for Entities, Value Objects, Aggregates, and Repositories to ensure technical robustness.

How does it improve overall code quality?

By enforcing a ubiquitous language and ensuring that core domain logic remains isolated from infrastructure concerns, resulting in more maintainable code.

Is DDD always the right choice for my project?

No, and this skill explicitly helps you identify when DDD might be overkill, such as for simple CRUD applications or projects with limited business logic.

Domain-Driven Design Architect

Name: Domain-Driven Design Architect
Author: joaquimscosta

byjoaquimscosta

•

개발자 도구

Provides expert guidance for implementing Domain-Driven Design principles to manage complex software architecture and business logic.

소개

This skill empowers Claude to act as a senior software architect specializing in Domain-Driven Design (DDD). It helps developers navigate the complexities of large-scale systems by defining bounded contexts, establishing a ubiquitous language, and implementing tactical patterns like aggregates, entities, and value objects. Whether you are deciding between a modular monolith and microservices or modeling intricate business rules, this skill provides the strategic frameworks and decision-making logic needed to ensure software remains maintainable and perfectly aligned with business goals.

주요 기능

Tactical pattern implementation for Entities, Value Objects, and Aggregates
1 GitHub stars
Architectural decision support for Monolith vs. Microservices transitions
Frameworks for establishing Ubiquitous Language and Event Storming
Identification and mitigation of 'anemic domain model' anti-patterns
Strategic design guidance for bounded contexts and subdomains

사용 사례

Refactoring a legacy monolith into clean, bounded contexts and subdomains
Modeling intricate business rules and invariants using domain events and aggregates
Designing the core architecture for a new, high-complexity business system

소개

주요 기능

Tactical pattern implementation for Entities, Value Objects, and Aggregates
1 GitHub stars
Architectural decision support for Monolith vs. Microservices transitions
Frameworks for establishing Ubiquitous Language and Event Storming
Identification and mitigation of 'anemic domain model' anti-patterns
Strategic design guidance for bounded contexts and subdomains

사용 사례

Refactoring a legacy monolith into clean, bounded contexts and subdomains
Modeling intricate business rules and invariants using domain events and aggregates
Designing the core architecture for a new, high-complexity business system