Preparing the next view without exposing private workflow data.
Data engineering · Phased project
Move customer preferences through a durable change feed
A fictional messaging service builds a read model from database changes. Restarts and schema changes can re-enable preferences that customers disabled.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
31h 15m + setup
Suggested stack
PostgreSQL · TypeScript · Object storage
Recommended next step
Start with ACDC-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice change-feed ordering, snapshots and privacy-preserving deletion.
What the team gains
Review whether replicated customer preferences remain correct during recovery.
Before you start
Create synthetic preference records and a replayable local change log.
Use adapters or fixtures without provisioning a production broker.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.