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)

Summary

In this chapter, we discussed the importance of language in system design and how precise and unambiguous terminology brings clarity. We also have a shared understanding of the domain for business people and developers. We also looked at how different industries use the same words to express different concepts and what consequences this has on domain modeling.

The code sample in this chapter showed how unclear language could make the implementation more complicated and less understandable. By introducing better language to the code, we made it much clearer and shorter and more concise. We made some implicit concepts more explicit, and it helped to get a better understanding of the business and improved the code quality. We also discovered many verbs that became part of the language, which is an essential addition to a glossary of nouns that are often seen as the only important...