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 finally got hold of the data that we put in the database. Now, our project contains several GET endpoints to retrieve the content of the underlying database. We used CQRS to create queries, which are completely separate from the models that we have in our domain. Certainly, we had to use aggregate types to query RavenDB, since these are the document types as well. This could be avoided by splitting the state model from the aggregate, but this is something you can explore yourself.

We embraced the power of native access to the database engine to do things that would otherwise be impossible or cumbersome to do if we'd just used repositories. That's because a repository type represents a collection of aggregates of a single type, and we would get in trouble if we needed to combine data from different aggregates in a single read model.

Read models...