DBMS > FatDB vs. Infobright vs. ToroDB vs. VoltDB

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

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

A MongoDB-compatible JSON document store, built on top of 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

Document store
Key-value store

Relational DBMS

Document store

Relational DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

github.com/torodb/server

www.voltdb.com

Technical documentation

docs.voltdb.com

Developer

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

8Kdata

VoltDB Inc.

Initial release

2012

2005

2016

2010

Current release

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

AGPL-V3

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

All OS with a Java 7 VM

Linux
OS X

for development

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

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

ADO.NET
JDBC
ODBC

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

Java

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and 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

Recent citations in the 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