The "Full" Mapping Strategy
Explore the full mapping strategy in hexagonal software architecture, where each use case has its own input and output models. Understand how this approach clarifies responsibilities between the web and application layers and helps manage complexity by defining clear command objects for each operation.
We'll cover the following...
We'll cover the following...
Another mapping strategy is what I call the “Full” mapping strategy as shown in the figure below.
Mapping
This mapping strategy introduces a separate input and output model per operation. Instead
of using the domain model to communicate across layer boundaries, we use
a model specific to each operation, for example, the SendMoneyCommand, which
acts as an input model to the SendMoneyUseCase port in the figure.
We ...