DBMS > FatDB vs. OpenTSDB vs. Postgres-XL vs. VoltDB

System Properties Comparison FatDB vs. OpenTSDB vs. Postgres-XL vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Scalable Time Series DBMS based on HBase

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

opentsdb.net

www.postgres-xl.org

www.voltdb.com

Technical documentation

opentsdb.net/docs/build/html/index.html

www.postgres-xl.org/documentation

docs.voltdb.com

Developer

FatCloud

currently maintained by Yahoo and other contributors

VoltDB Inc.

Initial release

2012

2011

2014

since 2012, originally named StormDB

2010

Current release

10 R1, October 2018

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

LGPL

Open Source

Mozilla public license

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

Java, C++

Server operating systems

Windows

Linux
Windows

Linux
macOS

Linux
OS X

for development

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

distributed, parallel query execution

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Telnet API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Erlang
Go
Java
Python
R
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

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

MVCC

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.

User concepts

Access control

Can implement custom security layer via applications

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

DB-Engines blog posts

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

show all

Recent citations in the news

Comparing Different Time-Series Databases
10 February 2022, hackernoon.com

MapR to help admins peer into dense Hadoop clusters
28 June 2016, SiliconANGLE News

A real-time processing revival - O'Reilly Radar
2 April 2015, O'Reilly Radar

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 Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

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

provided by Google News

Share this page