Check out Commanded to build DDD apps using CQRS and ES

[simisoz]

Hope this helps

[pzingg]

I have played with Commanded in the past. I was going to keep this application as close as possible to the original 2008 dddsample Java application. In that application, a "command" object is not a command in the CQRS/ES sense, it was just a container in the web interface that holds the parameters in a servlet request, even before those parameters become part of a DTO.

I may resort to a real Command and Event architecture if I ever get to this TODO item:

Apply all handling history events to a cargo (route specification + virgin itinerary).
  To do this, we will probably need to save the cargo's original route specification
  in the aggregate, and create new domain event topic(s) for route specification and/or
  itinerary changes.

If I get to this, I would probably start out by using Incident, on account of its simplified structure.