Writing eventually consistent read models into SQL tables with SqlReadModelProjector and SqlReadModelQuery, with the projector's position committed in the same transaction as its rows.

The ladder of read models in Sliceworkz EventModeling, from a live model projected per read to background projections, seeded reads and snapshots, and when to climb each step.

Rules people may break under conditions — declared once, checked by the command, judged by the kernel, previewed before anything is submitted

One place for each kind of check, and why a validation runs before events exist or never

How a command decides on history, raises domain events and gets its append checked against everything it read

Declaring the kinds of thing your events are about, with an id type per entity and type-safe tags

How a bounded context is declared, built from feature slices, deployed in parts, started and shut down

Why one stream per context is the DCB default, what a read and a consistency check cost, and what the in-memory store cannot tell you — the measured conclusions of the eventstore benchmark suite

Crypto-shredding — protecting personal data with Shreddable values, and erasing it by destroying keys rather than rewriting events

Electing one processor among several instances, with fencing tokens and priority-based handover