The previous episode in the series (part 3) can be found here. It's the time. First, to conclude this short series of blog posts dedicated to what's wrong with DDD. Second (and more important) - to talk about a practical alternative to DDD. Is there any?...
The previous episode in the series (part 2) can be found here. What was supposed to be a single, short blog post has grown to a series of at least four articles (because this one is not the grand finale yet). The good thing is that it was the readers&...
This is the 2nd post in the series. The 1st one can be found here. A short recap of where we are: to tackle the complexity of the domain & model, we should be able to tackle four challenges - F1/ how to model reality correctly; F2/ how to "...
A few weeks ago, we (myself & my two friends - Tomek & Wojtek, as a part of a community called CTO Morning Coffee) hosted an online X Spaces session on Domain-Driven Design (DDD). To be clear, this wasn't supposed to be an intro session; quite the contrary....
Problem: DDD practitioners acknowledge the importance of Ubiquitous Language (UL), only to ... treat it as a dry dictionary (a vocabulary for entities and value objects). Instead of analyzing the *deep* semantics of UL, we prefer to shape models from scratch using tactical framing (aggregates, repositories, etc.). That increases a margin...
> Quo vadis? (lat. Whither goest thou?) Last week I attended this year's edition of one of my favourite software craftsmanship-related conferences: DDD Europe [https://dddeurope.com/2020/]. It was a good time, I've met interesting people, attended a few workshops, enjoyed beautiful weather in always...
