DBMS > FatDB vs. HEAVY.AI vs. SQLite vs. VoltDB vs. Yaacomo

System Properties Comparison FatDB vs. HEAVY.AI vs. SQLite vs. VoltDB vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Widely used embeddable, in-process 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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

www.sqlite.org

www.voltdb.com

yaacomo.com

Technical documentation

docs.heavy.ai

www.sqlite.org/docs.html

docs.voltdb.com

Developer

FatCloud

HEAVY.AI, Inc.

Dwayne Richard Hipp

VoltDB Inc.

Q2WEB GmbH

Initial release

2012

2016

2000

2010

2009

Current release

5.10, January 2022

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Public Domain

Open Source

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

commercial

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 CUDA

Java, C++

Server operating systems

Windows

Linux

server-less

Linux
OS X

for development

Android
Linux
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

yes

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

none

Multi-source replication
Source-replica 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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

yes

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes

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

Users and roles with access to stored procedures

fine grained access rights according to SQL-standard

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.