Great work, Greg!
As I told you before,
I think CQRS refactors the marvellous work of Eric Evans
and effectively advances it one step further.
I humbly suggest a small change in the chapter organization
and give my impressions, comments and further suggestions about the
content.
1) Introductory section:
- more emphasis that storing Events is an alternative to storing
Structure + current State
- I don't see an obvious correlation between the use of RDBMS and
storing current State
- presenting how the chapter text is organized probably would make
reading easier
2) Making state change explicit in a domain model
- explain the concepts of command, transaction object, event and
snapshot
situated in the context of a more comprehensive and explicit view of
change in a domain model
- use the sale example as a guide for the explanation
and for contrasting with the alternative implicit view based on
structure + current state
3) Modelling gains
- use the retailer example to show in more detail the business
benefits
in terms of enhanced control and flexibility and better error
treatment
4) Implementation gains
- explain the technical benefits related to a better OO x RDB match
- explain the technical benefits related to parallel/distributed
architectures
- explain (in more detail) the associated costs
Lastly, the benefits are so important and numerous that they deserve a
summary.
Thanks for sharing your work with us.
I hope this feedback can represent an effective contribution.
Best Regards,
Rafael Peixoto de Azevedo
http://www.symprise.net
--
Subscription settings:
http://groups.google.com/group/DDDDReviewDiscussion/subscribe?hl=en