Implementing Domain-Driven Design

A Calculation Process

Here’s another example, this time from the current Core Domain (2), the Agile Project Management Context. This Service calculates a result from Values on any number of Aggregates of a specific type. Here I think there is no good reason to use a Separated Interface, at least not at present. The calculations are always performed the same way. Unless that situation changes, we shouldn’t bother separating the interface from the implementation.

Cowboy Logic

LB: “My stallion brings $5,000 per service, and I’ve got the mares lined up.”

AJ: “Now that horse is in his domain.”

Recall that the SaaSOvation developers originally created ...