Skip to content
Katabench
Try free

Split the Read From the Write

Medium About 25 min Katabench Pro

The history query formats its lines straight off the write-side aggregate, welding the two halves of a CQRS split together. A published snapshot already exists and sits unused; moving the aggregate into the contracts leaf instead trips the role rule.

The full brief is part of Katabench Pro

Pro opens this kata's brief, its starter code and its grader. To see how the track works first, try Break the Checkout Cycle, which is free.

How it is graded

You work across multiple files, and architecture rules turn the design boundaries into executable feedback.

C# architecture exercises →

What it practices

CQRS
Separate read models from the write-side aggregate they are derived from.
Integration events
Publish what happened across a module or service boundary as a stable contract, separate from in-process domain events.
Modular monolith
Modules talk through published contracts and own their data, never each other's internals.

Related katas