Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

If you have two days to learn the very basics of modelling, Domain-Driven Design, CQRS and Event Sourcing, here's what you should do:

In the evenings read the [Domain-Driven Design Quickly Minibook]{http://www.infoq.com/minibooks/domain-driven-design-quickly}. During the day watch following great videos (in this order):

  1. Eric Evans' [What I've learned about DDD since the book]{http://www.infoq.com/presentations/ddd-eric-evans}
  2. Eric Evans' [Strategic Design - Responsibility Traps]{http://www.infoq.com/presentations/design-strategic-eric-evans}
  3. Udi Dahan's [Avoid a Failed SOA: Business & Autonomous Components to the Rescue]{http://www.infoq.com/presentations/SOA-Business-Autonomous-Components}
  4. Udi Dahan's [Command-Query Responsibility Segregation]{http://www.infoq.com/presentations/Command-Query-Responsibility-Segregation}
  5. Greg Young's [Unshackle Your Domain]{http://www.infoq.com/presentations/greg-young-unshackle-qcon08}
  6. Eric Evans' [Acknowledging CAP at the Root -- in the Domain Model]{ht
@heimeshoff
heimeshoff / gist:7019be2ab8e8e20c3dffc848b47252f0
Created December 7, 2019 20:41
Ubiquituous language tradeoff
Which do you prefer and why?
Alternative ideas?
public Tickettransaction Buy_ticket(Attendee attendee)
{
if (tickets_available)
return Issue_Ticket(attendee);
else
return Not_Issued.Because("Box office should not allow to buy tickets, when there are none available.");
}