stream processing
Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.
-
7 min read
2025 Takeaways: The Year Real-Time got Real
In 2025, real-time decisioning shifted from a technical ambition to a business requirement. As streaming, AI, and edge computing matured,…
-
7 min read
Top 3 Kafka Streams Challenges
We’ve been writing a lot about challenges lately. We recently wrote about API challenges – now we’re discussing challenges with Kafka Streams. …
-
7 min read
Announcing Volt Active Data v9.1
I’m happy to announce the release of V9.1. In this release, we’ve simplified the integration of Volt Active Data into…
-
7 min read
5 Key Questions from our webinar, “Is Your Data Architecture Ready for Microservices?”
At our recent webinar, “Is Your Data Architecture Ready for Microservices?”, we received a number of questions from attendees about…
-
7 min read
Smart Stream Processing in the Age of 5G
In today’s digitally driven world, processing streaming data in real-time is a requirement for business success. The introduction of 5G…
-
7 min read
3 Benefits of Using a In-Memory NewSQL Data Platform for Smart Stream Processing
Traditional pub/sub systems such as Apache Kafka (and their numerous ever evolving stream processing avatars like Apache Samza, Apache Storm,…
-
7 min read
Volt Active Data Announces v9.0
We are hard at work on Volt Active Data and are pleased to release V9. This release focuses on new…
-
7 min read
Are Your Policy & Charging Systems Ready to Monetize 5G?
As 5G architectures are getting rolled-out, we are seeing a spike in RFPs from the largest mobile operators. The CSPs…
-
7 min read
Vlog: The History and Future of the Blurring of Stream Processing & OLTP
Recently, our founding Engineer, John Hugg, spoke at Berlin Buzzwords. This vlog contains the video of his presentation there. What’s…
Let’s Talk
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.