DDD Weekly: Issue #47

Event Sourced Aggregates Part 1: Outline of a typical implementation [blog] Christian Horsdal Gammelgaard. This is the first post in a series of posts that takes its offset in a design problem I’ve encountered repeatedly with event sourced aggregates: They grow every time a feature is added. Nothing (almost) is removed from them, so over time they grow very big and gnarly. Why does this happen? Because typical implementations of event sourced aggregates violate the Open/Closed principle.

50,000 Orange Stickies Later [video] Alberto Brandolini. Explore DDD 2017. It started like a tool for discovering Aggregates, then became a teaching tool for the DDD-illiterates. Now EventStorming is a platform for collaborative modeling whose depth spans from business and organizational design to implementation level software design. In this talk you’ll understand how different recipes can be leveraged for different goals and different audiences. And how those weird human brains behave, when we take them in unexplored places.

Scaling Event-Sourcing at Jet [blog] Lev Gorodinski. All things considered, the challenges of operating an event-sourcing platform are noteworthy, but its sound foundational principles continue to pay dividends as we evolve.

The Endless Battle: User-centered versus designer-centered [blog] Alan Cooper. The core tenet of all my work on interaction design is based on the simple notion that if you can identify the user, and learn what they are trying to accomplish, and why they want to accomplish it, you have all of the information necessary to generate a good design

KanDDDinsky Strategic DDD Workshop Review & Materials [blog] Nick Tune. I’m just home from a mind-blowing few days in Berlin for the KanDDDinsky conference. On day two of the conference, Zsofia Herendi and I ran our Advanced Strategic DDD workshop.

Building Reactive Systems Using Akka’s Actor Model and Domain-Driven Design [blog] Markus Eisele and Hugh McKee. With the explosion of mobile and data-driven applications, users are demanding real-time access to everything everywhere. System resilience and responsiveness are no longer “nice to have”; they’re essential business requirements. Businesses increasingly need to trade up from static, fragile architectures in favor of flexible, elastic systems.

One of the best and rarely emphasised benefits of #CQRS is… [tweet] Adam Dymitruk. One of the best and rarely emphasised benefits of #CQRS is enabling that “green field” development feeling though out a long-term, large project. This is gold!… Each read model can be treated like your little happy path 1st week with Ruby on Rails “rails new”. Harness happy devs!

Event Sourcing and CQRS with .NET Core and SQL Server [book] Nick Chamberlain. Launch will be underway very shortly for my new book about Event Sourcing and CQRS with ASP.NET Core and SQL Server. Make sure you keep an eye on your email for exclusive content related to the book, and take advantage of the pre-order pricing available NOW!