Book Image

Hands-On Domain-Driven Design with .NET Core

By : Alexey Zimarev
Book Image

Hands-On Domain-Driven Design with .NET Core

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.

Related Content you might be interested in

Current Title:

Small book image
Hands-On Domain-Driven Design with .NET Core
Alexey Zimarev
Apr, 2019 | 446 pages
Small book image
Domain-Driven Design in PHP
Christian Soronellas | Carlos Buenosvinos | Keyvan Akbary
Jun, 2017 | 394 pages
Small book image
Domain-Driven Design with Java - A Practitioner’s Guide
Premanand Chandrasekaran | Karthik Krishnan
Aug, 2022 | 302 pages
Small book image
Event-Driven Architecture in Golang
Michael Stack
Nov, 2022 | 384 pages
Table of Contents (14 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
Free Chapter
1
Why Domain-Driven Design?
Why Domain-Driven Design?
Understanding the problem
Dealing with complexity
Knowledge
Summary
Further reading
2
Language and Context
Language and Context
Ubiquitous Language
Language and context
Summary
3
EventStorming
EventStorming
EventStorming
Facilitating an EventStorming workshop
Our first model
Summary
Further reading
4
Designing the Model
Designing the Model
Domain model
Design-level EventStorming
Summary
Further reading
5
Implementing the Model
Implementing the Model
Technical requirements
Starting up the implementation
Transferring the model to code
Ensuring correctness
Domain events in code
Summary
6
Acting with Commands
Acting with Commands
Technical requirements
Outside the domain model
Handling commands
Application service
Summary
7
Consistency Boundary
Consistency Boundary
Technical requirements
Domain model consistency
Protecting invariants
Summary
8
Aggregate Persistence
Aggregate Persistence
Technical requirements
Aggregate persistence
Summary
9
CQRS - The Read Side
CQRS - The Read Side
Technical requirements
Adding user profiles
The query side
Implementing queries
Summary
10
Event Sourcing
Event Sourcing
Technical requirements
Why Event Sourcing
Event Sourced aggregates
Summary
Further reading
11
Projections and Queries
Projections and Queries
Events and queries
Building read models from events
Implementing projections
Cross-aggregate projections
Enriching read models
Persistent storage
Summary
12
Bounded Context
Bounded Context
The single model trap
Structuring systems
Summary
13
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think

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...
Previous Section
End of Section 4
Next Section