Event Sourcing

Trying to compromise the complexity of a database schema for read purposes while retaining any of the benefits of its relational nature often results in all of the pain and none of the gain.

One excellent way to speed up reads while allowing for complex writes is to maintain two datastores. One for reads and one for writes. This is what CQRS addresses and what I will be exploring in this talk. I will be covering how to keep datastores in sync, how the domain can facilitates that, and new datastores, such as EventStore, that become available when you embrace this way of thinking.

DDD/CQRS/ES in a nutshell.

• Raif Harik

  1 Recording

  Raif Harik is a software developer who has worked for a variety of companies as both a resident developer and as a contractor over the past 10 years. His work has been mainly server side development with a focus on line of business applications. In recent years he has become increasingly interested in and experience with client side development, still focusing on line of business, using javascript and various frameworks such as react, backbone and knockout.

• Austin .NET UG 56 Recordings

• DDD 5 Recordings
• CQRS 4 Recordings
• Event Sourcing 2 Recordings