   |
Contact Us | 1+978-528-4660 |
Voltage: The Blog for VoltDB Enthusiasts
We recently released the first supported version of a VoltDB client driver for Node.js applications. It was able to execute over 695K transactions per second. Since then we have been working on building a better driver and sought out help from the Node community and made a series of improvements.
Today I’m going to write about how to access VoltDB from a Node application. A sample application is included with the driver, the latest version of which can be downloaded from http://voltdb.com/products-services/downloads...
The purpose of this blog posting is to discuss strategies for handling decision support queries in Online Transaction Processing (OLTP) applications. First, I want to talk about the two classes of OLTP applications that I see in the marketplace.
The first is the traditional OLTP market that has been present for years, and is typified by purchasing Wall Street stocks. A collection of humans (stock brokers or end-users over the web) interact with an OLTP system to trade securities. The brokerage house (and end users for that matter) also want...
Technology markets are challenging enough to understand but, when you throw in the added noise that typically accompanies early markets, gaining real insights can be next to impossible. It is not unusual to have ten or more vendors in a particular segment and adjacent segments, and countless products attempting to solve similar customer problems. Needless to say, tech markets are rarely clear in the beginning.
Big Data is just such a market today. One of the challenges we face at VoltDB is making sense of this market and understanding where we fit. This, of course,...
Hi, I'm Henning Diedrich, co-founder and CEO of Eonblast, Inc. I'm a guest contributor to VoltDB's blog.
In February I was contacted by VoltDB about conducting a benchmarking project. The company had recently released an updated version of a Node.js client driver that had originally been authored by Jacob Wright, one of VoltDB’s community members. When I began looking into Node.js, it became clear that its architecture and scaling goals are quite well aligned with VoltDB’s, so I was...
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:
I’ve been writing Spring applications for a few years now and I’ve always been struck by the framework’s flexibility. A developer can write a web application in several distinct ways there is no discernible difference from an end user’s perspective. Freeing the developer from strict implementation processes and design patterns greatly expands the choices a developer can make, such that the developer can write an implementation that fits the specifics of just one application and then take a completely different approach that is more suitable for another application.
...
Last week I gave a webinar entitled OldSQL vs. NoSQL vs. NewSQL for New OLTP. If you missed the live webinar and want to view the recorded version, you'll find it here (you may need to scroll down to find it). Below is a list of questions that live webinar attendees asked, in no particular order. If you have follow-on questions, reply to this post and I or someone else from VoltDB will answer them.
This is the first in a series of blog posts in which I will explore various aspects of On-Line Transaction Processing (OLTP). In this post, I'll examine main memory storage as an alternative to disk for traditional and “New OLTP” systems.
Traditional relational DBMSs, Hadoop and most of the NoSQL offerings store their data on disk. In contrast, VoltDB is a main memory DBMS.
First, it should be noted that main memory is getting very cheap. It is straightforward to put 50 Gbytes of memory on a $5,000 server. Beefy servers these days have 10 times...
On June 14, 2011, Jacob Wright (Twitter: @jac_) published a pure Javascript Node.js driver for VoltDB. It is a great driver and it does just about everything a developer could ask for. It is pure Javascript so it runs everywhere and is written asynchronously so it follows the best practices of Node as well as those of VoltDB, which performs best when queries run asynchronously.
VoltDB is evolving constantly and we have just released a our own version of the...
Gavin Clarke published an interesting piece in The Register this morning entitled MongoDB straps SQL to Google’s MapReduce. The article covers several points, but the gist (from my read) goes something like this:
|
©VoltDB Inc., All rights reserved |