How chebureque/iddd_samples works
Overall Structure and Main Components
– AgilePM Context (iddd_agilepm)
– Collaboration Context (iddd_collaboration)
– Identity & Access Context (iddd_identityaccess)
– Common Infrastructure/Components (iddd_common)
Within Each Bounded Context, Represent the Layers
– Application Layer: This includes application services (for example, the AgilePM application services, Collaboration’s calendar/forum application services, IdentityAccess’s RESTful services and command handling).
– Domain Layer: Represent the domain model objects, aggregates, and domain events. The AgilePM context has a rich domain for product, backlog items, sprints, and teams. Collaboration deals with event sourcing aspects and CQRS (split between command handling and the query/read model). IdentityAccess covers identity, authentication, authorization, and user management.
– Ports & Adapters Layer: Show the adapters used for messaging (RabbitMQ and SlothMQ listeners in AgilePM and Collaboration), persistence adapters (LevelDB in AgilePM, JDBC/MySQL-based projections in Collaboration, and ORM/Hibernate in IdentityAccess), as well as the RESTful resource adapters in IdentityAccess.
Interactions & Data Flow
– For instance, from application services to domain models.
– Indicate the integration between the command-side (Event Sourcing) and the query-side (MySQL projections) in the Collaboration context, showing the slight consistency trade-offs.
Infrastructure Components
• Persistence Mechanisms:
– AgilePM explicitly uses a LevelDB (pure Java) key-value store.
– Collaboration uses LevelDB for the event journal as well as MySQL for its CQRS read model.
– IdentityAccess uses Hibernate (with MySQL) for object–relational mapping.
• Messaging Components:
– Identify RabbitMQ (and its listeners/publishers) in IdentityAccess and some parts of AgilePM and Collaboration.
– Also indicate the role of SlothMQ listeners in agilepm and collaboration.
• That Docker is used for test/experiment setups (MySQL and RabbitMQ containers started by startContainers.sh).
Architectural Patterns & Technologies
• Domain-Driven Design principles by clearly demarcating bounded contexts.
• Layered architecture in each context (Application, Domain, Ports/Adapters).
• Use of Event Sourcing & CQRS in the Collaboration context.
• For IdentityAccess, highlight the integration of RESTful interfaces, ORM (Hibernate), and event notifications via messaging.