StateVec cluster performance: throughput and latency
Measurements for Verify mode and Performance mode at batch sizes 256 and 1024 on AWS c9gd.xlarge * 3 cluster, plus local RAM-backed results, checkpoint settings and benchmark setup.
Blog
Engineering notes for StateVec.
The core makes decisions. Surrounding systems build business views.
How the StateVec transaction core owns business state while learners and projectors build query views, notifications and decision inputs from committed history.
Verify mode: replicate commands and compare execution results
From leader simulation to follower verification, quorum commit and ordered apply: how Verify mode checks execution and builds a verifiable transaction history.
Choosing between Verify mode and Performance mode
Choose Verify mode for pre-commit execution verification or Performance mode for a shorter replication path. Both retain Raft ordering, ACID transactions and durability.
How StateVec differs from SpacetimeDB and Aeron Cluster
Compare the transaction core, developer responsibilities, replication and execution verification in StateVec, SpacetimeDB and Aeron Cluster.
Rapid modeling, controlled evolution, auditable history
How plugin upgrades, historical audit views and business-invariant checks support a business engine as its rules evolve.
Raft History, Verified Execution, and Recovery
The current durability boundary: Raft WAL, verified execution, and recovery from a selected checkpoint plus committed suffix.
Power of Simulation
Why deterministic engines can compute, reject, commit, replay, and verify from a cleaner boundary.
Stacked Data View
How layered state keeps records, unique keys and indexes consistent during execution: read precedence, deletions, ordered merges, batch visibility and business refusals.