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)

Enriching read models

At this moment, we have a collection that contains a single object of type ReadModels.UserDetails in memory. This object represents a single user, so we can find out what display name the user has if we have the user ID. This is helpful, but how can we use it to show the full details of our classified ad? There are two ways of doing this, considering that we are within a single-application boundary and use the same store (currently in memory) for all read models.

When developers start to deal with data that is spread across multiple data sources, the most obvious method that comes to their mind is to aggregate data on the edge. One of the most popular techniques is to build BFF. When the frontend needs to get some aggregated data, it sends one request to a single API endpoint at the backend, and the API itself calls different data sources and merges the...