Domain-driven design has given us an excellent guide to tackle the complexity by keeping the domain concepts at the core of our designs. By defining ubiquitous language we demarcate context boundaries and divide the system into well-defined bounded contexts. Typically, we create a small world of aggregates and entities within these bounded contexts to implement… Read More KAPPA your Domain Model into the Data-Mesh Architecture
Apply learnings of Pet Helland’s paper “Data on the Outside versus Data on the Inside” on Event Driven Systems… Read More Events on the Outside vs Events on the Inside
When it comes to the events, the big debate is about the contents of its body. Martin Fowler has written a great post on this topic. Some devs argue that events should carry the complete load with it, I am calling them Fat Events (Event Carried State Transfer) in this blog.And then we have others… Read More Events: Fat or Thin
Domain Driven Design (DDD) is the widely accepted and proven pattern to build applications dealing with complex domains. Not many applications manage to maintain the clear boundaries between bounded contexts as they grow bigger. Even if it is realised, the high costs of refactoring discourage to bring things back on track. The cost of refactoring gets… Read More Decouple Entity Framework based monolith to well defined bounded contexts.