DBMS > Infobright vs. MySQL vs. VoltDB

System Properties Comparison Infobright vs. MySQL vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Widely used open source RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.79
Rank	#207	Overall
	#97	Relational DBMS

Score	964.98
Rank	#2	Overall
	#2	Relational DBMS

Score	1.21
Rank	#164	Overall
	#74	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.mysql.com

www.voltdb.com

Technical documentation

dev.mysql.com/doc

docs.voltdb.com

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

since 2010, originally MySQL AB, then Sun

VoltDB Inc.

Initial release

2005

1995

2010

Current release

9.0.0, July 2024

11.3, April 2022

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Java, C++

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users with fine-grained authorization concept

no user groups or roles

Users and roles with access to stored procedures

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL is the DBMS of the Year 2019
3 January 2020, Matthias Gelbmann, Paul Andlinger

MariaDB strengthens its position in the open source RDBMS market
5 April 2018, Matthias Gelbmann

The struggle for the hegemony in Oracle's database empire
2 May 2017, Paul Andlinger

show all

Recent citations in the news

30 years of MySQL, the database that changed the world
6 May 2025, theregister.com

Scaling Amazon RDS for MySQL performance for Careem’s digital platform on AWS
13 May 2025, Amazon Web Services (AWS)

MySQL Explained: Your Guide to Mastering This Powerful Database
29 August 2024, Oracle

Node.js MySQL Tutorial: Create and Manage an Employee Database [Updated]
14 May 2025, Simplilearn.com

MySQL at 30: Still important but no longer king
12 May 2025, InfoWorld

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Aims for Fast Big Data Development
29 January 2015, ADTmag

VoltDB Announces Key New Hires
26 October 2021, citybiz

MemSQL, VoltDB Vie For In-Memory Big Data Role
12 February 2015, InformationWeek

VoltDB Adds Geospatial Support to Its Operational InMemory SQL Database
30 January 2016, App Developer Magazine

provided by Google News

Share this page