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 identified the domain model and agreed that the model represents some part of real life, which is targeted to solve some specific problem. We also discussed the importance of behavior and that it is an essential part of the model that is often overlooked and even ignored.

Along the way, we introduced the CQRS pattern. It separates commands as something to be done inside the model and that represent behavior, from queries that have the only purpose of retrieving state.

Then, we got more elements for the EventStorming modeling technique in order to model detail in more depth, moving toward something that we can start implementing in code. We recognized that these new elements match well with the CQRS paradigms.

Finally, we went through the modeling session of our sample domain and got more insight into how the core part of the system should work, so we...