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)

Designing the Model

Many think of domain models as data models. You can easily see this by searching for the domain model on Google—all the things you find are data diagrams or class diagrams. Although class diagrams sometimes contain some useful behavior (methods), even this does not happen that often. However, since the complexity of business is rarely in its data, we need to realize that behavior is an integral part of a domain model.

Big Picture EventStorming helps us to understand the whole business or a part of it, but we need to take it further to get to the implementation. Design-level EventStorming is just that—we look at the part of the system that is most interesting for us and dive deeper into it, discovering more events and new flows.

In this chapter, we will cover the following topics:

  • What does the domain model represent?
  • Patterns and anti-patterns...