Browse files

Update Fohjin.DDD.Example/ReadMe.txt

  • Loading branch information...
1 parent e234077 commit 4ba55487d23d8e034fbaa24d04fce380da0c9d2a @MarkNijhof committed Sep 15, 2012
Showing with 8 additions and 9 deletions.
  1. +8 −9 Fohjin.DDD.Example/ReadMe.txt
@@ -1,4 +1,3 @@
x86 vs x64
When running the example on a x86 machine you have to go into the /Lib/sqlite/bin/ folder
@@ -13,7 +12,7 @@
I have also written a few blog posts about this CQRS example application:
CQRS a la Greg Young
Intro: I have had the pleasure of spending a 2 day course and many
geek beers with Greg Young talking about Domain-Driven Design
specifically focussed on the Command and Query Responsibility
@@ -22,22 +21,22 @@ how Eric Evans describes it in his book and has adapted mostly the
technical implementation of it.
CQRS Domain Events
Intro: As you may have seen in my previous post “CQRS à la Greg Young”
now our domain aggregate root is responsible for publishing domain
events indicating that some internal state has changed. In fact state
changes within our aggregate root are only allowed through such domain
CQRS Domain State
Intro: This morning Aaron Jensen asked a really interesting question
on Twitter “Should Aggregate Roots en Entities always keep their state
if it is not needed for business decisions? Is firing events and
relying on the reporting store enough?”.
Specifications <-- explaining the base test fixture class
Intro: I received a couple questions about the Specification Framework
that I use in the CQRS example and thought lets talk about that for a
bit. The first thing that should be underlined is that this is not a
@@ -47,14 +46,14 @@ dependencies. I got the initial bits from Greg Young at his DDD course
which I extended a little bit for my specific needs.
CQRS Event Sourcing
Intro: So after reading this blog post by Rob Conery about Reporting
In NoSQL where he explains very well what the problem is when using a
RDBMS for persisting the state of your domain, or really anything that
is written with Object Orientation in mind.
CQRS Event Versioning
Intro: When using Event Sourcing you store your events in an Event
Store. This Event Store can only insert new events and read historical
events, nothing more nothing less. So when you change your domain
@@ -64,14 +63,14 @@ historical events belonging to the same behavior. The Event Store
needs to stay intact, that is one of its powers.
CQRS Scaling
Intro: Scalability is one of the several different benefits you gain
from applying CQRS and Event Sourcing to your application
architecture. And that is what I wanted to take a closer look at in
this post.
Using conventions with Passive View
Intro: I was reading Ayende’s blog post about building UI based on
conventions and thought; hey I have something similar in my CQRS
example. And since this is the least interesting part of the whole

0 comments on commit 4ba5548

Please sign in to comment.