Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.
8 min read
We’re happy to announce the release of Volt Active Data V9.2. In this release, we introduce features that will speed…

8 min read
YCSB is a well known benchmark that was devised by a group at Yahoo! Research led by Brian F. Cooper.…
8 min read
Introduction The “Telecom Application Transaction Processing” benchmark was devised to model telco system behavior for benchmark purposes. The documentation describes…
8 min read
Introduction In this post I’d like to highlight voltdb-chargingdemo, which I’ve recently made available on github. Most demos are designed…
8 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…

8 min read
Recently, we hosted our webinar, “Is Your 5G Data Architecture Ready for Microservices?”, hosted in conjunction with FierceWireless. This unique…
8 min read
Last month we hosted our webinar, “Is Your 5G Data Architecture Ready for Microservices?”, hosted in conjunction with FierceWireless. It…
8 min read
Last month we hosted our webinar, “Is Your 5G Data Architecture Ready for Microservices?”, hosted in conjunction with FierceWireless. It…

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

8 min read
In today’s digitally driven world, processing streaming data in real-time is a requirement for business success. The introduction of 5G…
8 min read
5G architecture recommends a service-based approach to enable end-to-end software defined network functions. Initially virtualization-based – and now heading toward…

8 min read
Traditional pub/sub systems such as Apache Kafka (and their numerous ever evolving stream processing avatars like Apache Samza, Apache Storm,…
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.