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 finally started to use the term Bounded Context. It is often overlooked by people who started learning DDD. In Eric Evans's book, Bounded Context, it is explained in the strategic design part, which starts quite late in the book. A lot of useful patterns are introduced in that book before getting to the concept of Bounded Context and naturally, people start using what they know and sometimes find that to be enough.

But make no mistake, the power of DDD is not in aggregates and repositories. If you have a single model for a large, complex software system, having aggregates and repositories won't help you. When a large number of developers work with a single model, they suffer from an extensive need for coordination, conflicting changes, regression bugs, cognitive overload, and constant context switching. The fact that contexts aren't articulated...