From Context to Flow

From Context to Flow is the advanced Domain-Driven Design bridge volume of the NEXUS-1 series. Where From Domain to Twin introduced the essential DDD vocabulary, this book takes the next step: it shows what happens when a domain model begins to move across boundaries as events, contracts, workflows, failures, retries, projections, audits, and delayed consistency.

This is not a microservices implementation guide. It is the book that should come before microservices. Its central question is simple:

Before we split a system into services, do we truly understand its boundaries, its language, its ownership, and its flows?

Using the NEXUS-1 digital-twin demonstrator as a coherent teaching system, the book follows a realistic architectural flow:

Alarm Raised → Alarm Flood Detected → Root-Cause Case Opened → Evidence Attached → Verdict Issued → Recommendation Generated → Audit Entry Written → Compliance Review Triggered

This flow crosses several bounded contexts: ReactorFleet, Instrumentation, AlarmManagement, RootCause, DigitalTwin, ReinforcementLearning, Audit, Compliance, and Reporting. That makes it an ideal environment for advanced DDD because every step forces a serious architectural question: who owns the rule, who publishes the event, who reacts to it, what must remain private, what becomes a public contract, and what happens when the next context is temporarily unavailable?

The book explains advanced DDD patterns in practical language: context maps, upstream/downstream relationships, customer/supplier relationships, conformist relationships, shared kernel, anti-corruption layers, published language, domain events, integration events, outbox, inbox, idempotency, dead-letter handling, process managers, sagas, compensation, timeouts, and eventual consistency.

It also draws a clear line between things that are often confused:

A domain event is not automatically an integration event.
An audit entry is evidence, not workflow.
A bounded context is not automatically a microservice.
A recommendation is not a command.
A projection is not the source of truth.
A retry is not a business decision.
A compensation is not a rollback.

Every chapter keeps the NEXUS-1 standing rule: nothing claims to exist that does not. The book does not pretend that distributed architecture is free. Every pattern is explained with its benefit, its cost, and its honest boundary.

This book is written for C#/.NET developers, software architects, and advanced learners who already understand the basics of DDD and want to move from modelling to architectural flow. It is especially useful for readers who want to understand how a modular system becomes ready for microservices without rushing into deployment boundaries too early.

By the end of the book, you should be able to look at a large system and ask better questions:

Which context owns this language?
Which aggregate protects this rule?
Is this event internal, external, or only an audit fact?
Does this workflow belong inside one application service, or does it need a process manager?
Is this dependency healthy, or does it require an anti-corruption layer?
Can this context become a microservice, or is it only a module with a fashionable name?

The goal is not to make the system more distributed.
The goal is to make the system more honest before distribution begins.

This book is dedicated to Eystathios Andreadis — my brotherly friend and an outstanding surgeon — who reminds us every single day that there are still people whose integrity, compassion, and dedication set them apart.

Author: Grigorios Kyriakos Agathangelidis
Greek name: Γρηγόριος Κυριάκος Αγαθαγγελίδης
Also searchable as: Αγαθαγγελίδης Γρηγόριος, Αγαθαγγελιδης Γρηγοριος, Grigorios Agathangelidis.