I recently discovered through eventual consistency that my bounded contexts were not properly aligned with the business. I won’t lie, it took me quite a while to make this realization. This was most likely the case in many situations I’ve had in the past. Because of this realization, I wanted to let out some of my thoughts about eventual consistency and business alignment. Dependent Bounded Context I’ve often encounter situations where a bounded context requires information that another bounded context is responsible for. I’d like to use a simple example I’ve heard from Udi Dahan. In the context of an Ecommerce site. A… Read More »Eventual Consistency and Business Alignment
Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.
Keep it simple. There isn’t much of a need to go out of your way adding extra layers of abstraction. Any data access framework or ORM you might be using will already be creating a good enough level of abstraction. With linq (IQueryable) being implemented in NHibernate, Entity Framework, or Linq to SQL, ORM du jour, you already have your a level of abstraction to your data source. Need to query your read model from the client? Single page application maybe? Ok… you need one more layer. OData to the rescue. WCF Data Services provides an incredibly easy implementation with… Read More »CQRS: Read Model