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)

Adding user profiles

Before we start our journey to the read side of our application, we would benefit from adding some more concerns to the domain itself. So far, we have been concentrating on the core domain of classified ads. The core domain is what we should focus on when we create a new system. In our scenario so far, we have already made some progress implementing the core domain, and the team is now discussing what would be an absolute must-have to add to the system before they start creating the prototypes.

You might remember that we have already partially addressed the concern of who owns the ad. We have the OwnerId property of the UserId type in the ClassifiedAd aggregate, but so far we haven't got the location where OwnerId comes from. Apparently, our system needs to have users that must register themselves before creating new ads. We need to know who they are...