Why this matters
- VaultCommerce fraud aggregates store session counts in
vaultcommerce-fraud-detector-order-count-store. - Standby replicas (
num.standby.replicas=1) reduce recovery time on failover. - State store disk must be sized — RocksDB grows with distinct keys.
- Interactive queries expose state via REST for debugging (use carefully in prod).
Stream task
RocksDBLocal state
Compacted topic
RocksDB and changelog
Every state store maps to internal changelog topic applicationId-storeName-changelog. On restore, consumer replays changelog from beginning (or checkpoint). VaultCommerce monitors changelog lag during redeploys — large state = long restore.
Key points
- State store — local key-value materialization of aggregations/joins
- Changelog topic — compacted backup of state store updates
- RocksDB — embedded LSM storage under Kafka Streams
- Standby replica — warm copy for faster task migration
- Restore consumer — replays changelog on task assignment
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Standby and caching
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.