DDD Studio is currently in closed alpha. Signing in with Google or GitHub counts as your application to join. Please note that applying does not guarantee access.

Product · Model

Then get precise.

The model is not a drawing. It is a structured domain model with several views on it, and every operation passes through a rule engine — so what you draw is what exports.

Context Map

Cataloging
core9 terms
Partnership
Lending
coreteam:lending
LendingInside the context · Static View
Actor
Member
issues →
LoanAGGREGATE
acceptscheck outreturn
publisheschecked outreturned
guards◆ copy-lent-at-most-once
→ projects
Read model
My loans
Scenario · a second loan is refused
given checked out { copy: 42 }
when check out { copy: 42 }
then rejected · copy-lent-at-most-once

Same names on every level: the rule the aggregate guards is the rule the scenario tests.

The Context Map with Cataloging and Lending in a partnership; zoomed into Lending, the Loan aggregate with its commands, events and a rule, and a Given-When-Then scenario that tests exactly that rule.

Flows

Tell behaviour as slices

A flow is a named, ordered story over the same model, not a second copy of it. Everything on a flow exists in the model, and changing it there changes it everywhere.

  • Command, read-model and event-handler slices in lanes
  • Process managers that trigger commands on events or timers
  • Example data on the tiles, tag filters to focus a part of the flow

Flow view · borrowing a book

Trigger
API
Persistence
Event
Cataloging
1 · Acquire a book
Librarian
acquire
Book
acquired
Lending
2 · See what is available
Member
available copies
Availability
acquired← from 1
3 · Check out
Member
check out
Loan
checked out

Each column is one slice: one cause and its effect, read left to right as the story. A read-model slice draws the event it projects from where that event is produced.

The Flow View: three slices in the lanes trigger, API, persistence and event, grouped into the contexts Cataloging and Lending.

Guardrails

A compiler for your domain model

Composing semantic building blocks instead of arbitrary shapes is what lets the tool help: it suggests sensible next steps, checks cardinalities and scopes, and tells you what is still open.

  • Invalid connections are refused, with the reason
  • Unfinished elements stay visible as drafts and are left out of exports
  • Outdated scenarios and slices are flagged

Static view · the editor knows the rules

Cataloging
Book
acquireacquired
Lending
Loan
check outchecked out
Reservationdraft

“check out” cannot publish “acquired”. A command only publishes events of its own aggregate. To react across contexts, add a policy.

3 drafts openReservation · no events yetPolicy · idempotency not chosen
The editor refuses an invalid connection with a reason and keeps unfinished elements visible as drafts.

Five views, one model

Context Map

Contexts and external systems, relationships with the established patterns, subdomains and the team that owns each context.

Static View

Aggregates, actors, policies, read models, event handlers and process managers, with quick-add suggestions.

Flow View

Slices over the model in the order you tell them.

Scenarios

Given–When–Then per aggregate or read model. Refusals cite the rule they rest on.

Glossary

Each context's words, what they mean there, and the words it rejected — searching the wrong word still finds the right one.

Notes and tags

Pin free-text notes to a canvas and tag any element, without changing the model.