DBMS > GigaSpaces vs. HEAVY.AI vs. OrigoDB vs. RocksDB

System Properties Comparison GigaSpaces vs. HEAVY.AI vs. OrigoDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

A fully ACID in-memory object graph database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Graph DBMS
Search engine

Spatial DBMS

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.gigaspaces.com

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

origodb.com

rocksdb.org

Technical documentation

docs.gigaspaces.com/latest/landing.html

docs.heavy.ai

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Gigaspaces Technologies

HEAVY.AI, Inc.

Robert Friberg et al

Facebook, Inc.

Initial release

2000

2016

2009

under the name LiveDB

2013

Current release

15.5, September 2020

5.10, January 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

Open Source

Apache Version 2; enterprise edition available

Open Source

BSD

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++, .Net

C++ and CUDA

C++

Server operating systems

Linux
macOS
Solaris
Windows

Linux

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

XML can be used for describing objects metadata

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

JDBC
ODBC
Thrift
Vega

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

.Net
C++
Java
Python
Scala

All languages supporting JDBC/ODBC/Thrift
Python

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes, event driven architecture

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role-based access control

fine grained access rights according to SQL-standard

Role based authorization

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.