Набір Domain-Driven Design

Record an EventStorming session: events timeline, commands, actors, policies, read models, hotspots, context candidates

Core, supporting and generic classification: differentiation and complexity scores, quadrant chart, findings, expected movement, decisions

Strategic question, users and needs, value chain, evolution assessment, quadrant map and map source, movement, inertia, options and gameplay, doctrine, decision, signposts

Design one DDD bounded context: purpose, strategic classification, roles, inbound/outbound messages, language, rules, metrics

Glossary of domain terms per bounded context with synonyms to avoid, examples, code names, owners and change rules

One scenario as numbered commands, events and queries between contexts: notation, sequence diagram, message register, checks, failure paths

Map bounded contexts and their DDD relationships (ACL, OHS, conformist, shared kernel), team ties and evolution plan

Team types, interaction modes, cognitive load, as-is and target team diagrams, findings and a dated evolution plan

A team's public interface: type, mission, owned services, versioning, channels, ways of working, roadmap, interaction modes

Event-sourced service design: fit check, event catalogue, versioning and upcasting, store, projections, idempotency, crypto-shredding

Service canvas: bounded context, owner, APIs and events, data owned, dependencies, SLOs, scaling, config, deploy, observability