Glossary
Consistent terminology for the domain model, application architecture, and event-store infrastructure.
Command
Domain decision
Domain event
Event store
Projection
| English | Русский | Definition |
|---|---|---|
| event | событие | A record of something that has happened |
| domain event | событие домена | An event expressing a fact relevant to the domain model |
| stream | поток событий | An ordered event sequence identified by a stream ID |
| projection | проекция | A transformation that processes events to build or update derived data |
| subscription | подписка | A mechanism for delivering events to a consumer |
| read model | модель чтения | A model structured to serve queries |
| write model | модель записи | A model that supports domain behavior and validates state changes |
| append | добавление событий | Adding events to the end of a stream |
| replay | воспроизведение | Processing stored events again without re-executing the original commands |
| expected version | ожидаемая версия | The stream version required for an append to be accepted |
| checkpoint | контрольная точка | A saved processing position used to resume consumption |
| aggregate | агрегат | A consistency boundary containing entities and value objects accessed through an aggregate root |
| command | команда | A request to perform an operation; it can be rejected |
| Event Sourcing | Event Sourcing | Persisting state changes as events and reconstructing state from their sequence |
| event store | хранилище событий | Storage designed to persist and retrieve event streams |
| durable subscription | устойчивая подписка | A subscription with processing progress that persists across consumer restarts |
| transient subscription | временная подписка | A subscription without a persisted consumer checkpoint |
| materialized view | материализованное представление | Stored results of a transformation or query, maintained for subsequent reads |
| rehydration | восстановление состояния | Reconstructing aggregate state from stored events, optionally using a snapshot |
| snapshot | снимок состояния | Derived aggregate state saved together with its stream version |
| eventual consistency | согласованность в конечном счёте | A consistency model in which replicas or derived views converge once updates are propagated and applied |
| optimistic concurrency | оптимистический контроль конкуренции | Checking that the version used for a decision has not changed before accepting a write |
| bounded context | ограниченный контекст | The boundary within which a particular domain model and its language apply |
| aggregate root | корень агрегата | The entity through which an aggregate is accessed and its invariants are enforced |
| invariant | инвариант | A rule that must remain true across valid state changes |
| command handler | обработчик команды | An application component that coordinates execution of a command |
| repository | репозиторий | An abstraction for loading and persisting aggregates |
| CQRS | разделение ответственности команд и запросов | Using separate models for state-changing operations and queries |
| DDD | предметно-ориентированное проектирование | An approach to software design centered on a domain model and a shared language |
| integration event | интеграционное событие | An event published under a contract for communication across application or bounded-context boundaries |
Projection and read model, command and event, aggregate and stream are related concepts—not interchangeable names. Use one term consistently for each concept.