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

4 min read
First post in a series on features of Volt Active Data Version 9.2. Version 9.2 of Volt Active Data introduces…
4 min read
We’re happy to announce the release of Volt Active Data V9.2. In this release, we introduce features that will speed…

4 min read
YCSB is a well known benchmark that was devised by a group at Yahoo! Research led by Brian F. Cooper.…
4 min read
Introduction The “Telecom Application Transaction Processing” benchmark was devised to model telco system behavior for benchmark purposes. The documentation describes…
4 min read
I’m happy to announce the release of V9.1. In this release, we’ve simplified the integration of Volt Active Data into…

4 min read
At our recent webinar, “Is Your Data Architecture Ready for Microservices?”, we received a number of questions from attendees about…

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
We are hard at work on Volt Active Data and are pleased to release V9. This release focuses on new…

4 min read
Need 640K TPS and perfectly accurate running totals? Volt Active Data has the answer. But it’s not what you’d expect……
4 min read
Recently our team put together notes from the field into a new whitepaper: The 5G Revolution. In it, we discuss…
4 min read
Happy New Year! To ring in 2019, we have a new version of Volt Active Data available to you with…

4 min read
At our recent webinar, “NoSQL vs. NewSQL: Evaluating Database Technologies for 2019”, we received a number of questions from attendees…
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.