If you can feel a bad smell in the air, you can tell that something is rotten. The very same rule applies to sniffing out transactions spanning several entities to make a business operation complete. You may call these entities aggregates, you may call them Foo or Bar, but if transactions are wide, you're in … Continue reading The guiding smell of wide transactions
Does a team colleague reads your DNA daily? Do you know what's going on in your cell number A345BC345T343? Is there a single cell in your body that can ask your whole body to stop for a second? I hope the answer to all these questions is NO. Let's take a look at all these … Continue reading Aggregates, services, systems as cells, organisms, society
A while ago I sealed up a few bottles of home made wine (created only for oenology purposes ofc.) Somehow, maybe because of winter's time, my memory resurfaced these moments and connected them with something I'm working now currently, which is connected with Domain Driven Design. Is there any way the process of producing wine … Continue reading Wine, grapes and DDD
This is the end of mini series related to Top Domain Model. Let's quickly go through all the topics we've covered.
Make things implicit (more) explicit. This is the mantra we often here, but when touching the reality of software development, often forget, because of the magic beauty of technology, tooling, etc. Should we repeat this, when modelling domains as well?
Is it possible to stick just to aggregates to model your domain? Is it possible to make it any better with services or maybe another tool is needed?
In this episode, we will revisit this idea by referring to the good old-fashioned Twitter and its timelines. How timelines are created? Is everyone treated equally? Is it only aggregates' identities that should be pivoted or maybe our thinking as well?