In this chapter, we dove deeply into the topic of aggregate persistence. You have seen many challenges that are associated with what is known as impedance mismatch, when we can clearly see that databases aren't exactly happy to persist complex object graphs as is due to specific requirements that different types of databases have. Also, you learned about using the repository pattern to abstract the persistence and keep both our domain model and the application service away from the database-related concerns.
You learned how to use RavenDB to persist our aggregate as a document, and what challenges we might encounter on this road. It became clear that document databases are, in general, more suitable for persisting complex objects, but some concerns still need to be addressed, like handling identities and exposing properties.
This chapter also covered the topic of...