ddd-by-examples/library
Library
Ce projet est une implémentation de référence des design patterns Domain-Driven Design, de la modélisation de domaine fonctionnelle et de la coordination d'état pilotée par les événements. Il démontre l'application de design patterns stratégiques et tactiques pour gérer des exigences métier complexes.
L'implémentation utilise un modèle de domaine fonctionnel avec des fonctions pures et des objets immuables pour gérer les transitions d'état et les effets de bord. Il dispose d'une architecture Command Query Responsibility Segregation (CQRS) pour séparer les modèles de lecture et d'écriture, ainsi qu'une coordination pilotée par les événements pour maintenir la cohérence à travers les limites métier autonomes.
La base de code intègre une architecture monolithique modulaire utilisant des contextes bornés (bounded contexts) et un découpage hexagonal pour isoler la logique centrale de l'infrastructure. L'assurance qualité est gérée via une suite de développement piloté par le comportement (BDD) qui reflète le langage omniprésent pour vérifier les scénarios métier et des tests automatisés qui imposent des contraintes architecturales.
Le projet applique ces patterns à un domaine de gestion de bibliothèque, couvrant la maintenance du catalogue de livres, les flux de travail de circulation, les validations de réservation et le suivi des retours en retard.
Features
- Domain-Driven Designs - Provides a reference implementation of strategic and tactical Domain-Driven Design patterns to manage complex business requirements.
- CQRS Patterns - Implements Command Query Responsibility Segregation to separate read and write models for optimized data access.
- Repository Patterns - Uses repositories as a mediator layer to decouple domain logic from specific data source implementations.
- Functional Domain Modeling - Employs pure functions and immutable objects to manage business processes and error states without side effects.
- Repository Pattern Abstractions - Decouples the domain model from the persistence layer using interfaces that treat data storage as in-memory collections.
- Functional State Management - Utilizes pure functions and immutable objects to manage business state transitions and side effects.
- Layered Implementations - Isolates core business logic from external frameworks through hexagonal layering to ensure independence.
- Command Query Responsibility Segregation - Separates data modification logic from data retrieval logic to optimize performance and scalability.
- Command Query Responsibility Segregation Patterns - Implements a separation of read and write models to optimize data access and update operations.
- Modular Monoliths - Organizes the system into independent bounded contexts within a single unit to maintain clear boundaries.
- Hexagonal Architecture Implementations - Implements ports and adapters to isolate core business logic from external frameworks and infrastructure.
- Bounded Contexts - Divides the system into independent modules with explicit linguistic and functional boundaries to isolate business complexity.
- Behavior Driven Development - Implements behavior specifications to validate business logic using a domain-specific language.
- Domain Event Synchronization - Captures state changes as explicit events to coordinate data consistency across autonomous business boundaries.
- Type-State Patterns - Uses the type system to represent business states as distinct classes, ensuring valid transitions at compile time.
- Architecture Rule Enforcement - Employs automated tests to validate dependency rules and prevent infrastructure leaking into core business logic.
- Data Consistency Models - Implements immediate and eventual consistency mechanisms to maintain data integrity across different business boundaries.
- Event-Driven Coordination - Coordinates interactions between decoupled business modules using structured domain events.
- Business Scenario Mappings - Identifies and prioritizes specific business cases to map high-level requirements to detailed architectural design patterns.
- Architectural Constraint Validation - Uses automated tests to enforce architectural boundaries and prevent infrastructure dependencies from leaking into core logic.
- Business Requirement Validations - Uses behavior-driven development to verify that implementations match discovered business requirements.
- Story-Based Test Organization - Implements a domain-specific language for tests that mirrors business stories and ubiquitous language.
- Behavior-Driven Testing - Implements testing patterns that prioritize business stories and ubiquitous language over internal implementation details.
- Domain Event Handlers - Uses domain events to execute side effects and synchronize state across different business aggregates.
- Event Persistence - Captures and stores state changes as explicit events within repositories to support event-driven architectures.
- Domain Driven Design Samples - Modular monolith library system using advanced DDD techniques.
- Domain Driven Design - A comprehensive reference implementation of domain-driven design principles.
