Book Image

Hands-On Domain-Driven Design with .NET Core

By : Alexey Zimarev
Book Image

Hands-On Domain-Driven Design with .NET Core

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)

Outside the domain model

We strive to keep our domain model intact from anything that is related to infrastructure, persistence, execution, and communication. This makes the domain model pure and keeps it focused on the business. However, we still need to create the whole system around it, keeping the domain model as the system core.

The whole world of runtime surrounds our domain model, and in this section, we are going to dissect all necessary components that are required to build a proper system and look at how these components need to be bound together, with each other and with the domain model.

Exposing the web API

Our system needs to have some visibility to users, and therefore, at some point, we will need to build a...