Insights on building, scaling, and enforcing real-time decisions in modern data-driven systems.
5 min read
I’m happy to introduce a fully featured, high-performance Volt Active Data client for the go language. The golang client is…
5 min read
I recently joined Volt Active Data as the lead Solutions Architect responsible for helping prospects, customers and partners in the…
5 min read
Let me start by making an arrogant statement: There is no such thing as eventual consistency. There is only ‘Immediate…
5 min read
Volt Active Data hired Kyle Kingsbury, creator of the Jepsen Tests, to build a new, stronger, Jepsen test especially for…
5 min read
There’s a very simple distinction in the database world that tends to be ignored. Your database either: Or, it If…
5 min read
Innovation in the telecommunications industry has been led primarily by hardware vendors, offering differentiating capabilities to carriers. This has created…
5 min read
This post is a contribution from Cheryl Wiebe, Partner of Advanced Analytics at Teradata West Region. If you follow Gartner,…
5 min read
This blog was adapted from a post that first appeared on LinkedIn. There’s an interesting article in The Economist on consumer IOT.…
5 min read
Volt Active Data was a sponsor of the recent In-Memory Computing Summit in San Francisco. I always enjoy going back…
5 min read
Ryan Betts is one of Volt Active Data’s founding developers, and is currently our CTO. He’s been designing and building…
5 min read
Check out or documentation site to learn more about Volt Active Data Cross Data Center Replication. In section 11.3, you’ll…
5 min read
We’ve added a new feature in Volt Active Data v6.6: support for joins in materialized views. We’re very pleased to…
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.