I’m very happy to announce the release of VoltDB 2.5.  Consistent with prior releases, 2.5 includes one major new feature, Database Replication, combined with other significant work in and around the VoltDB core engine.  I’d summarize our 2.5 engineering investments as follows:

• Database Replication.  As I’d previously described here, Database Replication is the headline feature of 2.5 (until recently, we referred to the feature as WAN replication).  It allows VoltDB databases to be automatically replicated within and across data centers.  Available in the VoltDB Enterprise Edition, Database Replication ensures that every database transaction applied to a VoltDB database is

… Read more

The subject of my last blog post was an introduction to VoltDB Replication, one of the major product additions that we’ve been working on.  Well, with this post, I’m happy to announce that we’ve recently pre-released VoltDB Replication to selected users to perform beta-level validation!

VoltDB WAN replication involves duplicating the contents of one database cluster (known as the master) to another database cluster (known as the replica). The process of retrieving completed transactions from the master and applying them to the replica is managed by a separate process called the Disaster Recovery (DR) agent.

The DR agent is critical … Read more

This is the first in a series of posts about WAN replication, a VoltDB feature that’s currently under development.  It provides a high level overview of our direction.  More detailed posts will follow as we progress through our engineering iterations.

As an in-memory transactional DBMS, VoltDB delivers breakthrough performance and scale.  Two of the product’s most significant innovations, however, are in database availability and durability:

• Availability – VoltDB delivers high availability (HA) via a synchronous multi-master feature called K-safety.  When a database is running “K-safe”, multiple (two or more) node replicas are kept transactionally consistent.  If one of those nodes

… Read more

In this blog post I want to build on the example given by John and dig a little deeper into how VoltDB ensures global ordering and replication in the face of failures.

I am going to drill down on the following paragraph

Site 1 and site 4 both receive the message from the initiator. They then each do the same work in parallel. Since each individual site performs transactions one at a time, the transaction information is put into a queue at site 1 and queue at site 4. Work is pulled from the queues at

… Read more