CQRS with ASP.NET MVC - A Year On

Sign in to queue

Description

Last year, we looked at CQRS and Event Sourcing, and we primarily looked at using a framework called Ncqrs. https://channel9.msdn.com/Series/mvcConf/mvcConf-2-Ashic-Mahtab-CQRS-and-Event-Sourcing-with-MVC-3 While the concepts are great, taking on such a dependency may be worrying to some. In this session, we will look at how we can use pure and simple C# (and some F#) features to apply these patterns and achieve re-usability, modularity, aspect orientation, scalability etc. in our web applications. A lot of the concepts covered can be applied immediately to a large number of applications without requiring massive rewrites.

Day:

1

Level:

300

Embed

Download

Download this episode

The Discussion

  • User profile image
    HeartattacK

    The code for this session is available at https://github.com/ashic/aspConf-cqrs

    Also, if you liked the talk, please consider rating it here http://speakerrate.com/speakers/11533-ashic-mahtab

  • User profile image
    Preaching​Llama

    If all the events are replayed in memory when the application starts, how can this model scale to use multiple application servers?

  • User profile image
    HeartattacK

    This is just one way of doing it. For certain scenarios, you would want persisted projection data. But even without that, there are many ways of having different nodes have a subset of the projection data in memory. When starting up, they would take a hit and take longer to start up, but when started, would act pretty much like any disk backed memory store. Another option is to persist the in memory set periodically to disk. When starting up, the node would read in the persisted set into memory and play back subsequent events (and not all from the beginning of time). There are a lot of other options - you could write books on this topic. However, this a sub-90 minute talk and it's not really possible to cover everything in that limited time.

Add Your 2 Cents