An issue commonly encountered when working with DDD aggregates, is getting aggregates to interact; with each other, and other services around it. If you are unfamiliar with the aggregate pattern, Martin Fowler sums it up [http://martinfowler.com/bliki/DDD_Aggregate.html] nicely. Transactions shouldn't happen between aggregates,

You can read the first post of the series - Handling immutable types part 1 [https://www.marccostello.com/handling-unwieldy-immutable-types] - If you haven't already. -------------------------------------------------------------------------------- In my last post [https://www.marccostello.com/handling-unwieldy-immutable-types], I went on to explain some of the benefits of immutable types in

Immutable types are nice. We like immutable types. They are massively undervalued when building software. Many of us don't take the time to consider the purpose of the class we are creating and how it fits into the structure. Why immutable types? It is much easier to reason