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)

Events and queries

One thing that I've heard many times when talking about event sourcing with developers who are new to this technique, is the claim that event sourcing is not suitable for reporting. Let's first define what reporting is. Normally, we think of it as the ability to retrieve the system state from the database on demand, using filters and grouping, with minimal latency. Relational databases are quite good for this purpose since this was the main reason that relational databases were invented in the first place. If you are old enough, you might remember a short period of hype around object databases (ODBMSes, short for object-oriented database management system) in the mid-1990s. What could be better than storing entire objects to a database, without taking care of the impedance mismatch? In a world that is largely dominated by different kinds of relational...