• DDD Weekly: Issue #6 - DDD Decoded - The Aggregate and Aggregate Root Explained (Part 1) Mike Mogosanu. “modelling an aggregate has nothing to with object oriented design, but everything to do with paying attention to the domain expert and really groking the domain.” Build an application using microservices and CQRS IBM developerWorks: Felicia Tucci. “…regardless of the complexity of the business logic, with these techniques the implementation of new commands, events, and event listeners can become essentially a purely mechanical and repetitive process. [DDD Weekly]
• What is an implementation detail? - I bet you encounter (and use) the term "implementation detail" a lot. But what it means, exactly? And how to see if something is an implementation detail? [Enterprise Craftsmanship]

Permalink | From 25 July 2016 to 31 July 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• DDD Weekly: Issue #5 - Adaptive Consulting’s Reactive Trader Cloud Adaptive Consulting. Reactive Trader Cloud is a real-time FX trading platform demo showcasing reactive programming principles applied across the full application stack. Improvements have been made across the board since Reactive Trader v1. The UI is revamped with a modern Javascript framework (React), and an event sourcing approach is used by the backend services for data resiliency. Introducing Domain Map - The Domain Modeling Tool Mike Mogosanu. [DDD Weekly]
• DDD Weekly: Issue #4 - Reactors, Channels, and Event Streams for Composable Distributed Programming Aleksandar Prokopec, Martin Odersky. The “Reactor Model” offers some interesting improvements to the Actor Model. The Beating Heart of CQRS on the CLR Paulmichael Blasucci. CQRS and F# - 2 of my favorite things. Here is the source for the Message Router code from Quicken Loans’ Github repository. Hanselminutes: Exploring the Orleans Distributed Virtual Actor Model with Richard Astbury Scott Hanselman. Greg Young, in his talk “A Decade of DDD, CQRS, Event Sourcing,” mentions that “the rise of Actor Models has also happened around the same time as the rise of Event Sourcing, which also happened around the same time as the rise of Functional Programming. [DDD Weekly]
• Unit testing anti-patterns: Structural Inspection - This post is about the practice of Structural Inspection in unit testing and why I personally consider it an anti-pattern. [Enterprise Craftsmanship]

Permalink | From 18 July 2016 to 24 July 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• EventStorming – What You Need to Know - The real power of eventstorming is how it focuses on outcomes, not activities. Why is this powerful? It gives you options. That is according to Dan North at his recent talk at DDD eXchange in London with Skill Matter. I know there is a lot of interest in eventstorming right now. It is of particular […] [Learn CQRS and Event Sourcing]
• DDD Weekly: Issue #3 - Event Storming - What You Need to Know Daniel Whittaker. I think we should all be excited about techniques that improve strategic design like Event Storming. Strategic and Collaborative Domain-Driven Design Nick Tune. Interesting approach to calling the “ubiquitous language” the “business glossary” to gather more appeal from the domain experts. Elm and Event Sourcing Marco Perone. Imagine all of your apps having theTime Travel Debugger… Introduction to Event Sourcing and CQRS Beau Simensen. [DDD Weekly]
• DDD Weekly: Issue #2 - Agile France 2016 – Decentralized Architecture Cyrille Martraire. Notes from an “open-space session” (also an interesting topic) about architecture at different scales across teams and beyond. Offers “orientations” for developing rules that allow emergence of new patterns, while maintaining consistency within the company. 10 Lessons from a Long Running DDD Project - Part 2 Jimmy Bogard Lessons 6-10 from Jimmy’s previous post where his team realizes the benefits of targeting a single, cohesive group. [DDD Weekly]
• Growing Object-Oriented Software, Guided by Tests Without Mocks - This is a review of the Growing Object-Oriented Software, Guided by Tests book (GOOS for short) in which I’ll show how to implement the sample project from the book in a way that doesn’t require mocks to be tested. Growing Object-Oriented Software, Guided by Tests Without Mocks Let me first explain why I’m doing a review of this book. If you read this blog regularly, you probably noticed that I’m pretty much against using mocks in tests. [Enterprise Craftsmanship]

Permalink | From 04 July 2016 to 10 July 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT