To model your data, there are different reasons for using a write side and a read side.
RavenDB allows you to do some interesting things modeling the different read and write structures of a database.
For example, ETL allows you to perform automatic transformation of your data from the write database to the read database which is also important when you have different services consuming each one.
The fact that RavenDB is a document database gives you better behavior because you don’t have to worry that much about the modeling and you are able to do all sorts of interesting things using indexing, MapReduce, to transform your data.
An example might be when I am writing, I am adding a one-line item to an order. When I am reading, I need the entire order as a whole.
Watch RavenDB CEO Oren Eini show you how to use his Document Database as a CQRS read side data solution.
You will learn how to:
- use RavenDB as a CQRS read side database
- conquer the major technical and architectural challenges
- make modeling a lot easier using document database
- synchronize and update from an external event store like GetEventStore, Kafka, or an SQL Event Store
- deal with events that fail