THOUGHTS ON DYNAMIC CONSISTENCY BOUNDARY

Summary from the TLDR Data newsletter

Dynamic Consistency Boundaries let each event-sourced command protect only the events and types it reads, avoiding false conflicts from unrelated changes. The counterargument is that tag-based implementations merely relocate fixed boundaries into high-cardinality indexes, while schema changes, retagging, archiving, and query evolution become harder. Prefer multi-stream transactions and workflow streams unless narrower contention is proven.