When people start doing event sourcing, one mistake that often happens is that developers try to get into the comfort zone of the persisted state of their aggregates as soon as they can. So, many interpret read models as a way to keep the aggregate state accessible in a query able store. I have done the same thing in the past, so you can trust me on that. For the purpose of keeping an aggregate state in some database, I used a nice feature of Event Store—internal projections. You can check the list of available internal projections by visiting the Projections page of the Event Store web UI. One of those projections is $by-category, which links all events to special category streams. For example, $ce-ClassifiedAd will contain all events for the ClassifiedAd aggregate. You can inspect it yourself by visiting http://localhost:2113/web/index.html...
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.
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