Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.

4 min read
Traditional pub/sub systems such as Apache Kafka (and their numerous ever evolving stream processing avatars like Apache Samza, Apache Storm,…

4 min read
There is a massive difference between generating the input data needed by a Machine Learning model once (to prove a…

4 min read
Recently Forrester group has started to talk about “translytics” and Translytical Databases – databases that can “Deliver Analytics At The Speed…
4 min read
For decades, relational databases was the de-facto choice for financial service companies, until the 2000s where systems started to face…

4 min read
Credit card fraud is ever-growing and ever-present. According to the 2016 LexisNexis True Cost of Fraud study, the total cost…
4 min read
Editor’s Note: This piece originally appeared in DBTA. More companies are realizing that leveraging real-time data is the key to…
4 min read
In 2016, we partnered with Research Now to conduct a survey on a subject we take very seriously: data consistency.…
4 min read
We did a survey last year to see how enterprises viewed the need for “real time”(see https://www.voltactivedata.com/blog/worlds-apart-real-time-data-disconnect). Since we are…
4 min read
Billions and billions of transactions are executed each and every day by production-deployed Volt Active Data applications. A back-of-the-napkin calculation…
4 min read
We get a lot of questions about what Volt Active Data is, what it does well, and how it can…
4 min read
There’s a very simple distinction in the database world that tends to be ignored. Your database either: Or, it If…
4 min read
In my previous post, I described four applications (three implemented, one an example) that require, or at least strongly benefit…
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.