Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.
One of the key tasks during initialization of a Volt Active Data cluster is determining cluster topology. The topology includes…
A couple of weeks ago, an interesting issue came up in the field. The symptom was that the resident set…
Trying to choose a database to solve a problem (or a whole set of them)? Here’s a quick rundown of…
The sale and subsequent closure of FoundationDB cut short something of a grand experiment. FoundationDB, conceived as a Key-Value store,…
Working on distributed systems is fun, but not easy! As a software engineer at Volt Active Data, a big chunk…
The Lambda Architecture defines a robust framework for ingesting streams of fast data while providing efficient real-time and historical analytics.…
My name is Yetian Xia. I worked as a software engineering intern at Volt Active Data during the summer, working…
ndexes provide a classic “space for speed” trade-off. They add to the persistent memory footprint of your application data but…
The development team at Volt Active Data recently ran Volt Active Data v4.2 against the Yahoo Cloud Serving Benchmark (YCSB),…

Deleting records is often an afterthought when you’re first building a proof of concept with Volt Active Data, but it…
In a previous life I had a requirement that a web application scanned the expiration date of purchased content and…
There has been another round of online conversations about the CAP theorem as the internet community continues to discuss its…
Volt is the real-time decisioning layer for mission-critical systems, ensuring decisions are made and enforced immediately against accurate state, even under sustained load.
If your system cannot tolerate delayed enforcement, inconsistent behavior, or reconciliation after the fact, let’s start a conversation about whether a dedicated decisioning layer makes sense for your architecture.
Your applications are about to get a whole lot better.