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)

Our first model

Now let's try to practice and do an imaginary EventStorming session for our sample application domain. It is not easy to imagine how it would go since the most crucial aspect of any EventStorming workshop is the people and how they behave. We definitely cannot reproduce it here in writing, but we can imagine some discussions that can take place and the event flow that is produced.

We will be going through a fictitious EventStorming session, where a classified ads application will be discussed. A facilitator, let's call her Ann, has invited the following people to the workshop:

  • John, the company owner. He believes that the system will be the market leader due to its simplicity and unique features.
  • Mary is the UX (user experience) designer, and she has done some research on existing systems and has talked to some potential users.
  • Nick and Eve are full...