Favorites. GitHub Gist: instantly share code, notes, and snippets.

Domain-Driven Design Europe 2017
http://dddeurope.com - https://twitter.com/ddd_eu

If (domain logic) then CQRS, or Saga?

The “if” statement – the guard clause that makes sure that what shouldn’t happen, can’t happen. We see it all over our code base, especially in our domain logic. The thing is, when we use properties of domain objects in those if-statements, we don’t even realize that other agents may have just changed that data – or will change it just a second later. In essence, hiding behind those little “ifs”, are all kinds of race conditions and collaborative domains – the places where CQRS approaches are necessary. Join Udi for a different perspective on domain logic, CQRS, and long-running processes. It will be quite a saga.


Udi Dahan is one of the world’s foremost experts on Service-Oriented Architecture and Domain-Driven Design and also the creator of NServiceBus, the most popular service bus for .NET.

This presentation was recorded at GOTO Amsterdam 2019. #GOTOcon #GOTOams
http://gotoams.nl

Mathias Verraes - Programmer, Consultant & Advisor in Complex Environments & Spare Time Lego Train Constructor

ABSTRACT
Event Storming, Event Sourcing, CQRS, messaging, distributed systems … In one way or another, they’re all about time. Traditional modelling styles, focused on things and structures, are not the primary way anymore to build modern systems that handle complexity well. Object-oriented models tend to have an uneasy relation with events happening over time. The actual business processes, the heart of how organisations operate, end up hidden in the many calls between objects.
Temporal Modelling is the cure: build models and systems that make events and processes the first class building blocks of a domain model. In this talk, we’re going to look at how reasoning with time helps us better understand [...]

Read the full abstract here:
https://gotoams.nl/2019/sessions/817

https://twitter.com/GOTOamst
https…