Events should be as small as possible, right?
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Explores the question of how large or small events should be in event-driven systems. Argues that events should be treated as public API contracts, not just internal implementation details. Introduces the distinction between internal events (meaningful within a module) and external events (meaningful across the system). Warns against two extremes: bloated single events carrying all data, and overly granular internal events leaked externally — the latter being a path toward a distributed monolith. Recommends pragmatic event splitting and mapping strategies, including using projections and subscriptions in EventStoreDB to transform internal events into external ones.
