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)

Structuring systems

I know I've been painting a somewhat horrifying picture so far now—when software undeniably slips toward becoming an unmanageable clew of spaghetti code. You might be wondering: what's the point if we end up in the land of horror anyway? When we find ourselves there, we can start fresh, and learn from the past to build a new, shiny, bright system, with the newest technology and everything will be fine again. We will get back to the big rewrite topic later on, but for now, let's think about why the new system would be better than the old one.

No matter whether we are planning to create a new software system or to refactor the old one, there is at least one thing we can do to ensure that we keep our software in good shape for quite a long time. We might not be able to use the most beloved programming language, the new, shiny silver-bullet...