9 pages tagged.
The strategic patterns that keep a large codebase coherent: bounded contexts, context mapping, and where Kotlin helps.
Keeping a legacy integration from leaking its model into your domain, with a translation layer that earns its keep.
A cluster of objects treated as one unit for data changes, guarded by a root that protects its invariants.
A translation layer that keeps a foreign domain model from leaking across a context boundary.
The scope within which a single domain model stays consistent and unambiguous, governed by one ubiquitous language.
Naming the relationships between bounded contexts: partnership, customer-supplier, conformist, or a defensive anti-corruption layer.
A record of something meaningful that happened in the domain, letting bounded contexts communicate without sharing a model.
A workshop technique for surfacing domain events with the whole team in the room.
The shared vocabulary of a bounded context, used identically in conversation, code, and tests.