Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.
8 min read
Volt Active Data is already the go-to product for developing fast data applications because of its unparalleled performance, availability, and…
8 min read
Processing big data effectively often requires multiple database engines, each specialized to a purpose. Databases that are very good at…
8 min read
Openet, a leading independent supplier of real-time business support systems (BSS), ensures that more than 600 million mobile telecommunications users…
8 min read
In the Volt Active Data ebook, “Fast Data: Smart and at Scale,” Ryan Betts and I outline what we have…
8 min read
Introduction Last year we published YCSB benchmarks that compared IBM SoftLayer with Amazon Web Services. This generated a lot of…
8 min read
When you evaluate a database to use in your application stack, you usually look at the features, the performance, the…
8 min read
Continuous integration (CI) has become a fundamental process in many software-based companies in recent years. Fortunately, frameworks such as Jenkins…
8 min read
My name is Yiqun Zhang and I worked as a software engineering intern on the SQL core team at Volt…
8 min read
One of the key tasks during initialization of a Volt Active Data cluster is determining cluster topology. The topology includes…
8 min read
A couple of weeks ago, an interesting issue came up in the field. The symptom was that the resident set…
8 min read
Trying to choose a database to solve a problem (or a whole set of them)? Here’s a quick rundown of…
8 min read
The sale and subsequent closure of FoundationDB cut short something of a grand experiment. FoundationDB, conceived as a Key-Value store,…
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.