eventmodeling-identifying-outputs

To distinguish read models from domain events, identify immutable facts as events and map aggregated or computed values as derived projections. This prevents anti-patterns like modeling calculations as events during the design phase.

Event modeling for identifying outputs defines read models and query patterns derived from domain events. It creates a structured inventory mapping UI and processor data requirements to their source events.

Catalog read models by analyzing your event list to surface aggregated values as projections. This generates a structured inventory linking each read model to its source events and consumers.

Map UI data freshness by identifying which screens and processors need data and their required freshness. This query pattern mapping ensures read models satisfy specific consumer needs derived from event sources.

Calculations should be treated as projections to prevent architectural confusion between immutable facts and derived data. Modeling calculations as events creates anti-patterns that obscure clear data mapping in event-sourced architectures.