Skip directly to content

VoltDB Products/Versions

877,000 TPS with Erlang and VoltDB

Friday, April 5, 2013 - 12:00am

written by Henning Diedrich on April 5, 2013 

-Edited 5/2/13 by Henning Diedrich to correct configuration typos.

Running on a suitable EC2 configuration (see details below), with our new VoltDB Erlang driver we achieved 877,519 transactions per second.

I am Henning Diedrich [1], CEO of Eonblast Corporation[2] a games company. I would like to introduce the new Erlang VoltDB driver we created, a piece of software that allows two genre-defining technologies to work together: VoltDB [3] and Erlang [4].

The Driver

I first came to VoltDB on the hunt for a better database for heavy duty online-game

Announcing VoltDB v3.0 – Preview Release

Thursday, September 27, 2012 - 12:00am

written by John Piekos on September 27, 2012

Announcing VoltDB v3.0 – Preview Release

The next major release of VoltDB, version 3.0, is right around the corner.  In anticipation of this release, we’re announcing a preview release of the v3.0 offering, available immediately.  A brief overview and details on how you can preview this exciting release is found below.
What is VoltDB v3.0?

The VoltDB v3.0 release includes a set of user-visible features, including new SQL (specifically column functions), ad hoc SQL execution performance, Export enhancements, online schema changes, and a more

Announcing VoltDB v3.0 — BETA

Friday, November 9, 2012 - 12:00am

written by John Piekos on November 9, 2012 

The VoltDB Engineering Team is excited to announce the availability of the VoltDB v3.0 BETA.
The following provides a brief overview and details on how you can download this very important release.
What is VoltDB v3.0?

VoltDB v3.0 offers a set of user-visible features, including new SQL, indexable column functions, improved ad hoc SQL execution performance, export enhancements, online schema changes, and a more streamlined application-development process.

Clarifications on the CAP Theorem and Data-Related Errors

Thursday, October 21, 2010 - 12:00am

written by Mike Stonebraker on October 21, 2010 

There has been another round of online conversations about the CAP theorem as the internet community continues to discuss its implications on networked databases.   Coda Hale recently wrote a well received article titled, CAP paper by Gilbert and Lynch.

Scattered in the larger conversation is a continued mis-perception of my position regarding the CAP theorem. Coda writes “Michael Stonebraker’s assertion aside, partitions (read: failures) do happen.” Others have made similar comments, so let me set the record straight.

I have consistently and

Debunking Myths about the VoltDB in-memory database

Monday, May 12, 2014 - 12:00am

written by John Hugg on May 12, 2014

I’d like to take a quick moment to address some myths and misconceptions about VoltDB. Many people selling products who view VoltDB as competition seem to be repeating them. As you’ll read, much of what’s said is just plain FUD.

VoltDB is an in-memory database that has benchmarked at over 3 million transactions asecond on bare metal, and recently crushed previous performance records in the cloud, posting eye-popping YCSB (Yahoo! Cloud Service Benchmark) numbers on AWS, Amazon’s cloud platform.

Introducing VoltDB 3.0

Tuesday, January 22, 2013 - 12:00am

written by John Piekos on January 22, 2013

The VoltDB engineering team is thrilled to announce that VoltDB 3.0 is now available!  Over the past six months we’ve added a ton of features to VoltDB 3.0. This blog post lists the highlights, but that just scratches the surface. Look for future blog posts to dive into specific areas of version 3 functionality.

So let’s jump into what’s new in VoltDB 3.0…

Even Faster

VoltDB 3.0 has lower latency and more throughput than the VoltDB v2.x release.

JSON in VoltDB

Tuesday, February 5, 2013 - 12:00am

written by John Piekos on February 5, 2013

VoltDB 3.0 introduces the use of JSON-encoded columns to allow more flexibility in how you structure and interact with your data. New SQL functions and index capabilities let you work more naturally with JSON data while maintaining the efficiency and transactional consistency of a relational database.

How?  A VoltDB JSON Example

Let’s assume that you want to implement a single sign-on (SSO) application using VoltDB.  You wish to store the login session for a set of different online sites under a common username.

Making an Impact: VoltDB Engineering Interns

Friday, September 21, 2012 - 12:00am

written by John Piekos on September 21, 2012

Making an Impact: VoltDB Engineering Interns

Summer went by too fast in New England!  We are already missing our two engineering internship students, Xin Jia from Brown University and Zheng li from University of Massachusetts, Lowell.

During their internship, Xin and Zheng worked on numerous projects, explored new ideas, and helped accelerate the launch of product features. In short, they were big contributors to VoltDB.

Programming VoltDB – Easy, Flexible and Ultra-fast!

Monday, August 6, 2012 - 12:00am

written by John Piekos on August 6, 2012

You may believe that the only way to interact with VoltDB is through Java stored procedures.  To achieve maximum throughput, VoltDB stored procedures is the way to go.  You can achieve upwards of 100,000 transactions per second on a single node.  However, you can also achieve significant throughput by interacting with VoltDB conversationally, through ad hoc SQL statements, avoiding the need to pre-compile stored procedures.

This blog will discuss several approaches to interacting with VoltDB programmatically and cover the performance, in terms of

Visibility

Sunday, January 30, 2011 - 12:00am

written by VoltDB Team on January 30, 2011 

You cannot manage what you cannot measure”" - Peter Drucker

Most of us have heard this quote many times, though it’s probably more relevant to software development to say:

“You cannot manage what you do not measure”.

As software developers, we can figure out how to measure lots of stuff, and we can automate that measurement. We can even design in alerts to send us email when the measurements go out of bounds, or fail.

VoltDB’s End of Summer Engineering Update

Tuesday, August 28, 2012 - 12:00am

written by John Piekos on August 28, 2012

It’s been a busy summer here at VoltDB! Since spring the VoltDB Engineering team has released VoltDB four times (we’re operating on 3 week sprints) and delivered numerous product and performance enhancements.

Some of the major features we’ve recently released include:

  • Pause-less rejoin of failed nodes. Failed nodes can now be rejoined to the k-safe cluster without significant impact to the operational throughput of the cluster. This feature is available in the Enterprise edition of VoltDB.