EventCatalog | Domains

Overview

The Ordering domain represents a strategic core domain within the BookWorm system, responsible for managing the complete lifecycle of customer orders from creation through fulfillment. As a core domain, it embodies critical business capabilities that directly impact the organization’s competitive advantage.

Contact the author

Any questions? Feel free to contact the owners

1 services are in this domain

This service sends messages to downstream consumers

Domain Characteristics

Bounded Context: The Ordering domain has a well-defined boundary with explicit integration points with other domains like Basket, Catalog, and Notification through domain events.
Event Sourcing: The domain implements event sourcing as its persistence mechanism, storing the complete history of order-related events rather than just the current state. This approach provides a comprehensive audit trail and enables temporal queries and state reconstruction at any point in time.
Aggregates and Entities:
- Order (aggregate root) - Controls the consistency boundaries for order operations
- OrderItem (entity) - Books and quantities associated with an order
- Buyer (aggregate root) - Controls the consistency boundaries for buyer operations
- Address (value object) - Immutable shipping details

Domain Events

The domain produces and consumes various events including:

OrderCancelledEvent: Event raised when an order is cancelled
OrderCompletedEvent: Event raised when an order is completed
OrderPlacedEvent: Event raised when an order is placed

Business Rules and Invariants

Orders must contain at least one item to be submitted
Order status transitions follow a predefined state machine (e.g., Placed -> Completed or Cancelled)
Cancellation is only permitted before the “Shipped” status
Price calculations and summaries are validated against business rules

The domain handles complex business scenarios like partial fulfillment, order modifications, and cancellations while maintaining consistency and enforcing business rules throughout the order lifecycle.

Architecture diagram

Messages for this domain

Sends messages (3)

Quickly find the message you need by searching for the name, type, or summary.

Name	Version	Type	Summary
User Checked Out	v1.0.0	event	Represents an integration event when a user has completed the checkout process
Changed Order Status To Complete	v1.0.0	event	Represents an integration event when an order status is changed to complete
Changed Order Status To Cancel	v1.0.0	event	Represents an integration event when an order status is changed to cancel

Receives messages (14)