domain-events | 易学教程

Persistence and Domain Events with persistence ignorant objects

阅读更多关于 Persistence and Domain Events with persistence ignorant objects

问题 I've been studying on domain driven design in conjunction with domain events. I really like the separations of concerns those events provide. I ran into an issue with the order of persisting a domain object and raising domain events. I would like to raise events in the domain objects, yet I want them to be persistence ignorant. I've created a basic ShoppingCartService , with this Checkout method: public void Checkout(IEnumerable<ShoppingCartItem> cart, Customer customer) { var order = new

Where to raise persistence-dependent domain events - service, repository, or UI?

阅读更多关于 Where to raise persistence-dependent domain events - service, repository, or UI?

问题 My ASP.NET MVC3 / NHibernate application has a requirement to fire off and handle a variety of events related to my domain objects. For example, an Order object might have events like OrderStatusChanged or NoteCreatedForOrder . In most cases these events result in an email being sent, so I can't just leave them in the MVC app. I've read through Udi Dahan's Domain Events and dozens of other thoughts on how to do this sort of thing, and I decided on using an NServiceBus-based host that handles

Using Autofac with Domain Events

阅读更多关于 Using Autofac with Domain Events

问题 I'm trying to introduce domain events into a project. The concept is described in Udi Dahan's post - http://www.udidahan.com/2009/06/14/domain-events-salvation/ Here's the domain event code public interface IDomainEvent { } public interface IHandleDomainEvents<T> where T : IDomainEvent { void Handle(T args); } public interface IEventDispatcher { void Dispatch<TEvent>(TEvent eventToDispatch) where TEvent : IDomainEvent; } public static class DomainEvents { public static IEventDispatcher

Where to raise persistence-dependent domain events - service, repository, or UI?

阅读更多关于 Where to raise persistence-dependent domain events - service, repository, or UI?

My ASP.NET MVC3 / NHibernate application has a requirement to fire off and handle a variety of events related to my domain objects. For example, an Order object might have events like OrderStatusChanged or NoteCreatedForOrder . In most cases these events result in an email being sent, so I can't just leave them in the MVC app. I've read through Udi Dahan's Domain Events and dozens of other thoughts on how to do this sort of thing, and I decided on using an NServiceBus-based host that handles event messages. I've done a few proof-of-concept tests and this seems to work well. My question is what

Using Ninject with Udi Dahan's Domain Events

阅读更多关于 Using Ninject with Udi Dahan's Domain Events

I'm using Ninject in an MVC project and am trying to implement Domain Events following Udi Dahan's pattern http://www.udidahan.com/2009/06/14/domain-events-salvation/ In the extract below, the "Container" is used to resolve all the event-handlers for the particular type of event that has been raised. My question (& apologies if I am missing something basic) is how to do this with Ninject? In other words: How does the "Container" get set in this static class? Once I have a Container (Kernel?) what would be the Ninject syntax to resolve all the event handlers (which I'm assuming I would have to

Using Ninject with Udi Dahan's Domain Events

阅读更多关于 Using Ninject with Udi Dahan's Domain Events

问题 I'm using Ninject in an MVC project and am trying to implement Domain Events following Udi Dahan's pattern http://www.udidahan.com/2009/06/14/domain-events-salvation/ In the extract below, the "Container" is used to resolve all the event-handlers for the particular type of event that has been raised. My question (& apologies if I am missing something basic) is how to do this with Ninject? In other words: How does the "Container" get set in this static class? Once I have a Container (Kernel?)

Communicating between two Bounded Contexts in DDD

阅读更多关于 Communicating between two Bounded Contexts in DDD

I have few different Bounded Contexts in the domain. The validation of a CRUD operation is built in each Bounded Context. For example, I can create an entity called GAME only if the person creating it is a Group Leader . I have two Bounded Contexts (BC) in this example. One is the Game BC and the other is the User BC . To solve the problem, in the Game BC , I have to make a domain service call like IsGroupLeader() to the User BC before proceeding on creating the Game. I don't think this type of communication is recommended by DDD. I can have a User entity also in the Game BC , but I don't want

Communicating between two Bounded Contexts in DDD

阅读更多关于 Communicating between two Bounded Contexts in DDD

问题 I have few different Bounded Contexts in the domain. The validation of a CRUD operation is built in each Bounded Context. For example, I can create an entity called GAME only if the person creating it is a Group Leader . I have two Bounded Contexts (BC) in this example. One is the Game BC and the other is the User BC . To solve the problem, in the Game BC , I have to make a domain service call like IsGroupLeader() to the User BC before proceeding on creating the Game. I don\'t think this type