Skip directly to content

analytics

Announcing VoltDB 4.0: Enhanced In-Memory Analytics and Online Elasticity

Wednesday, January 29, 2014

The VoltDB engineering team is pleased to announce that VoltDB 4.0 is now available!

 

Bruce Reading, the VoltDB CEO is fond of saying that VoltDB contains lots of “yummy goodness”, and, while that is not a term we engineers use often, VoltDB v4.0 does indeed include a lot of new features.  The highlights of VoltDB v4.0 include:

  • Enhanced in-memory analytics capabilities with a host of new SQL support.
  • Greatly improved analytic read throughput performance.
  • Clusters can grow elastically, increasing both throughput and capacity, by adding nodes to running clusters without blocking ongoing operations.

From the Internet of People to the IoT and the Analytics of Things – industry examples

Thursday, June 23, 2016

This post is a contribution from Cheryl Wiebe, Partner of Advanced Analytics at Teradata West Region.

 

If you follow Gartner, Forrester and other industry analysts, you’re probably a reader of Gartner’s ‘Hype Cycles’ and Forrester’s ‘Waves’. According to Gartner, IoT is at the top of the Hype Cycle, and is forecast to deliver economic value of £1.2 trillion by 2020 ($1.7 trillion USD, for those of you who like to cover all the currency bases). Thus it should be obvious to all of us that the Internet of Things has taken the place of Big Data in the Hype Cycle.

 

I’d like to go further, using a

VoltDB Real-Time Analytics with JSON

Thursday, October 3, 2013

Consider the scenario where you are building an online multi-player game platform, where users can use the platform to create their own games. Such a platform would have the following high-level requirements:

 

  1. It needs to be able to process tens of thousands of write transactions, game state changes, per second. As each player makes a “move” or “action”, that needs to be recorded.
  2. It needs to be able to query player status and ranking. Each player’s ranking in relation to other players, for example, needs to be computed regularly, across all players and all games.
  3. It would need to support