Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> Comments on: CQRS – The Domain Events http://elegantcode.com/2009/11/20/cqrs-the-domain-events/?utm_source=rss&utm_medium=rss&utm_campaign=cqrs-the-domain-events Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Domain registration http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-2/#comment-64347 Domain registration Thu, 13 Oct 2011 09:46:00 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-64347 Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog. Excellent information  I charge we appreciate you your time and efforts you acquire in publishing this blog.

]]> By: Elegant Code » CQRS – Trying to make it re-usable http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50749 Elegant Code » CQRS – Trying to make it re-usable Sat, 28 Nov 2009 23:52:21 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50749 [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...] [...] I haven’t done anything with the event store yet, I don’t think the functionality will change much from the code in the example project. One thing that will remain the same is the dependency on interfaces, and not on specific implementations. This is obviously because it is good design practices. And it will enable us to mix this new approach and the approach using the BaseAggregateRoot class together with the same event store. The BaseAggregateRoot is discussed in detail here. [...]

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50605 Mark Nijhof Mon, 23 Nov 2009 16:17:35 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50605 <a href="#comment-50604" rel="nofollow">@Mike</a> Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool. @Mike
Perhaps you want to send me the code? I am currently working on something as well and some more input would be cool.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50604 Mike Mon, 23 Nov 2009 16:00:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50604 I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch. I finally got this working (I think). I had decomposed the event provider stuff out of the aggregate root base and the RegisterEvent call accepts a predicate for acceptance during dispatch.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50597 Mark Nijhof Mon, 23 Nov 2009 14:32:27 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50597 <a href="#comment-50582" rel="nofollow">@Szymon Pobiega</a> In my personal git repository I have already moved the different base classes to the event store so that the domain is only 'using' them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class. @Szymon Pobiega
In my personal git repository I have already moved the different base classes to the event store so that the domain is only ‘using’ them. And it would probably be doable to create some sort of proxy that does some stuff for you automatically without having the inherit from the base class.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50596 Mark Nijhof Mon, 23 Nov 2009 14:29:37 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50596 <a href="#comment-50578" rel="nofollow">@Mike</a> Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id. @Mike
Well each Entity in the collection is going to need an unique Id anyway (unique in the collection) so the event needs the Id of the Aggregate Root and it needs the Id of the Entity. So I am looking for a solution where both will be assigned automatically leaning towards what Jonathan suggested. But in the end you need to match Entities by their Id.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #482 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50588 Reflective Perspective - Chris Alcock » The Morning Brew #482 Mon, 23 Nov 2009 11:18:30 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50588 [...] CQRS - The Domain Events - Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...] [...] CQRS – The Domain Events – Mark Nijhof discusses the role of Domain Events in Command Query Responsibility Segregation code, showing their role in managing the state changes of the aggregate roots [...]

]]> By: Szymon Pobiega http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50582 Szymon Pobiega Mon, 23 Nov 2009 07:28:53 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50582 Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them. Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don't know if it is possible -- it is just an idea. Great job! Another very nice post. You convinced me to try this approach in practice. One thing I am concerned with is whether this approach is not overemphasizing the infrastructure. I would really like to put all those base classes in a separate library and just use them.

Obviously, it would be _ideal_ to make this model usable witch POCO approach. I really don’t know if it is possible — it is just an idea.

]]> By: Mike http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50578 Mike Mon, 23 Nov 2009 03:48:04 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50578 I have been messing with this and can't find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn't. I have been messing with this and can’t find a very clean way to dispatch to the correct instance given a collection of same-typed entities within an AR. The only solution I can figure is a predicate, maybe comparing an EntityId against the event, that an Entity base class can supply the MessageDispatcher to either accept the event or not. Otherwise, all entities of that type handle the event even when they shouldn’t.

]]> By: Mark Nijhof http://elegantcode.com/2009/11/20/cqrs-the-domain-events/comment-page-1/#comment-50539 Mark Nijhof Sat, 21 Nov 2009 14:38:58 +0000 http://elegantcode.com/2009/11/20/cqrs-the-domain-events/#comment-50539 <a href="#comment-50529" rel="nofollow">@Jonathan Oliver</a> This is an interesting approach, I'll take a look on how I would like to implement something like this. @Jonathan Oliver
This is an interesting approach, I’ll take a look on how I would like to implement something like this.

]]>