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)

Domain model consistency

When it comes to modeling, we often hear that data models need to be at the center of any system. If you want a good system, you need a good data model. I have heard that saying countless times in my career as a software engineer. One of my colleagues once said this, and then added: "I participated in a large project where we started with defining the data model, and, after eighteen months, the project was shut down because the model wasn't complete." Strangely, these two statements created no causal relationship for him, since the first statement was an axiom, and the project failure seemed to be caused by numerous reasons, but not by the fact that designing a single data model for complex systems is always a death march—many tables, directly and indirectly, connected to one another by foreign keys, an endless push for the third...