Practical tips for developers starting with event sourcing and event-driven architecture (EDA). Key advice includes aligning your architecture with the business domain using Event Storming or Event Modeling sessions, establishing a versioning strategy for events (with Greg Young's rule: if you can't convert an old event to the new format, it's a new event entirely), separating the append and publish steps into distinct processes to avoid data consistency issues during failures, and using sequential numbers rather than timestamps for event ordering to avoid clock-skew problems across systems.
Table of contents
Know your business domainMake a versioning strategyDo not append and publish events in the same processDo not rely on the timestamp for ordering102 Impressions