Week 15, year 2017
- Awkward Aggregate Root relationships and how to rethink them - I have an Order that can be split into multiple Shipments. A Customer orders Quantity X of Product Y, represented as a single OrderLine with Quantity = X. In order to optimize shipping costs, Quantity X of Product Y is split into Z number of Shipments…. [Nick Chamberlain on Nick Chamberlain]
- DDD Weekly: Issue #33 - The Tale of State and Behaviour, Part 1 with Scott Wlaschin [podcast] Three Devs and a Maybe. Part 1 and Part 2. “In this weeks episode we are lucky to be joined by Scott Wlaschin again, to discuss his recent ‘Thirteen ways of looking at a turtle’ talk.’” DDD eXchange 2017, April 27th - April 28th [conference] SkillsMatter. Strategic Domain Driven Design: Project Management Simplified [blog] Robert Reppel. “Just like realising the benefits from choosing a CQRS/ES based architecture requires a business domain- rather than technical mindset in order to properly establish transactional boundaries and to manage coupling and cohesion, DDD needs certain practices to be firmly established and continuously applied in order to be of value. [DDD Weekly]
- Temporal coupling and Immutability - This topic is partly covered in my Applying Functional Principles in C# Pluralsight course, Module 2. Here, I’d like to elaborate on how temporal coupling and immutability are related to each other. Temporal coupling Temporal coupling is coupling that occurs when there are two or more members of a class that need to be invoked in a particular order. A common example is the following: var calculator = new PriceCalculator(); calculator. [Enterprise Craftsmanship]