All Classes and Interfaces
Class
Description
Raised when a request would violate a business invariant enforced by the domain model or use case.
Active catalog price exposed to pricing use cases without leaking persistence details.
Application service that registers customers and backs the customer lookup module API.
Module API for resolving customers required by other modules.
Validated registration command for creating a customer.
Immutable customer view exposed by the customer module API.
Lifecycle status stored for a registered customer.
Outbound persistence port for customer registration and lookup.
Monetary value object used by pricing, orders and payments.
Application service that records notification intents after committed order and payment events.
Validated notification intent before it is persisted.
Module API for reading notification intents recorded by the notification module.
Lifecycle status stored for a notification intent.
Outbound persistence port for recorded notification intents.
Immutable view of a recorded notification intent.
Application service that coordinates customer lookup, pricing, order persistence and order events.
Order placement command accepted by the order module.
Domain event published after an order is persisted.
Validated order draft created after pricing has accepted each requested line.
Requested product line in an order command.
Validated priced line used to create a persisted order.
Immutable view of one persisted order line.
Module API for placing and retrieving orders.
Spring Boot entry point for the modular monolith order platform.
Lifecycle status stored for orders.
Outbound persistence port for submitted orders.
Immutable order view returned by the order module and REST layer.
Framework-independent payment state used to enforce authorization transitions.
Application service that prepares payments from committed orders and authorizes matching payments.
Domain event published after a payment is authorized.
Module API for authorizing and retrieving payments associated with orders.
Lifecycle status stored for a payment.
Outbound persistence port for prepared and authorized payments.
Immutable payment view exposed by the payment module API.
Outbound catalog port used by pricing use cases.
Price calculation for one requested product line.
Application service that reads the active catalog and calculates quote totals for order placement.
Completed quote returned by the pricing module.
Product quantity requested for pricing.
Module API for quoting product requests against the price catalog.
Raised when a request conflicts with an existing resource, such as a duplicate customer email.
Raised when a required aggregate or lookup target cannot be found.