So far, we have focused on state transitions in the system that are represented as events. When our domain model emits a new event, by definition, it means that we have put the system in a new state. State transitions are triggered by commands—that's why we have two APIs that are purposefully named ClassifiedAdCommandApi and UserProfileCommandApi. That shouldn't come as a surprise, since I have mentioned CQS and CQRS several times before in this book. Commands trigger methods of the aggregates, and following the CQS principle, none of those methods return anything, but instead change the system state. But no system can have only commands. Our users want to see something on the screen and it can't just be static texts and pictures. For our marketplace, the main purpose of the application is not that people can place classified ads in it; quite...
Hands-On Domain-Driven Design with .NET Core
By :
Hands-On Domain-Driven Design with .NET Core
By:
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.
Related Content you might be interested in
Current Title:
Hands-On Domain-Driven Design with .NET Core
Table of Contents (14 chapters)
Preface
Free Chapter
Why Domain-Driven Design?
Language and Context
EventStorming
Designing the Model
Implementing the Model
Acting with Commands
Consistency Boundary
Aggregate Persistence
CQRS - The Read Side
Event Sourcing
Projections and Queries
Bounded Context
Other Books You May Enjoy
Customer Reviews