DBMS > Infobright vs. TimescaleDB vs. VoltDB

System Properties Comparison Infobright vs. TimescaleDB 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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

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

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.timescale.com

www.voltdb.com

Technical documentation

docs.timescale.com

docs.voltdb.com

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Timescale

VoltDB Inc.

Initial release

2005

2017

2010

Current release

2.13.0, November 2023

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

Apache 2.0

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

Java, C++

Server operating systems

Linux
Windows

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full PostgreSQL SQL syntax

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with hot standby and reads on replicas

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

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

Recent citations in the news

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB for Azure Database for PostgreSQL to power IoT and time-series workloads | Azure updates
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

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

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

provided by Google News

Share this page