CQRS Info

Just put up http://cqrsinfo.com as many people have been asking for the information.

 

You will find there documents, 6-7 hours of video, and links to good material on the web.

This entry was posted in CQRS. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

12 Responses to CQRS Info

  1. gregyoung says:

    its the same site. domain squatters had grabbed the domain also try dddcqrs.com

  2. Vishal says:

    There isn’t anything on that site (cqrsinfo.com), its just brief plain text !! This is the one where you get most of CQRS: http://cqrs.wordpress.com/

  3. Eric Swann says:

    Looks like CQRSInfo.com is now some garbage advert site for pills and cigarrettes. Did the domain lapse? Is there an updated link that is still accurate?

  4. jessica says:

    the precious ideas you provided do help our team’s investigation for our company, thanks

  5. jessica says:

    Where event sourcing shines is that we can look at the SAME information in any possible way that they can conceive

  6. James says:

    Hi Greg,
    Where are you? Are you still in Vancouver? Great posts.

  7. kevin says:

    I don’t think the event sourcing for this purpose

  8. Greg says:

    dmitry:

    If the request is to add an attribute for the new idea then there is no way possible we can look at our old data that never had that property associated. We would have to make an equivalent change in both systems, you are correct.

    Where event sourcing shines is that we can look at the SAME information in any possible way that they can conceive (as seen in the example where they want to now look at items removed from a cart with 2:21 before the cart is checked out). We can make our OLTP models capable of doing this but in doing so we have to provide heuristics to what kinds of questions the business will want to ask.

  9. Dmitry says:

    Thanks for this link!

    It’s probably not a good place to comment but I found that the example mentioned in video that event sourcing allows to replay system from the beginning and thus be able to sustain to requirement changes to be quite “truth bending”.

    The example was about how marketing came with idea to check the theory about dependency of different sales on time and since event sourcing has time already included one could replay events to verify this theory (as opposed to static model when we don’t keep time of purchase).

    Apparently, would the theory was about dependency on family status of customer and you did not gather that in the first place any replay could not help either.

    In fact, I don’t think the event sourcing for this purpose (to sustain to reqs changes) is any better than a classical OLTP/OLAP division in “static world”. Although you could tell that this division is the form of event sourcing in the first place:)

    I would like to hear little more compelling reasons when and why we should choose event sourcing.

  10. Thanks Greg – this is very helpful – the more ammo and education on this pattern the easier it is to explain it :)

  11. Thanks for sharing Greg. Not sure what the twitter exchange between you and Jeremy was about – but your material and 6 1/2 hour class is excellent – and very ‘concrete’. I think you’re making a valuable contribution to the community.

  12. TerryBD says:

    I downloaded the example the other week, and read the comments of people criticizing the “simplicity”. I must say, there are concepts that I don’t understand but want to learn. 6 1/2 hours of video sounds about right though. I shall be downloading that.

    Thank-you.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>