Book Image

Hands-On Domain-Driven Design with .NET Core

By : Alexey Zimarev
5 (1)
Book Image

Hands-On Domain-Driven Design with .NET Core

5 (1)
By: Alexey Zimarev

Overview of this book

Developers across the world are rapidly adopting DDD principles to deliver powerful results when writing software that deals with complex business requirements. This book will guide you in involving business stakeholders when choosing the software you are planning to build for them. By figuring out the temporal nature of behavior-driven domain models, you will be able to build leaner, more agile, and modular systems. You’ll begin by uncovering domain complexity and learn how to capture the behavioral aspects of the domain language. You will then learn about EventStorming and advance to creating a new project in .NET Core 2.1; you’ll also and write some code to transfer your events from sticky notes to C#. The book will show you how to use aggregates to handle commands and produce events. As you progress, you’ll get to grips with Bounded Contexts, Context Map, Event Sourcing, and CQRS. After translating domain models into executable C# code, you will create a frontend for your application using Vue.js. In addition to this, you’ll learn how to refactor your code and cover event versioning and migration essentials. By the end of this DDD book, you will have gained the confidence to implement the DDD approach in your organization and be able to explore new techniques that complement what you’ve learned from the book.
Table of Contents (14 chapters)

Summary

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...