DBMS > Graph Engine vs. Graphite vs. HEAVY.AI vs. OrigoDB vs. RocksDB

System Properties Comparison Graph Engine vs. Graphite vs. HEAVY.AI vs. OrigoDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.57
Rank	#73	Overall
	#5	Time Series 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.graphengine.io

github.com/graphite-project/graphite-web

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

origodb.com

rocksdb.org

Technical documentation

www.graphengine.io/docs/manual

graphite.readthedocs.io

docs.heavy.ai

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Microsoft

Chris Davis

HEAVY.AI, Inc.

Robert Friberg et al

Facebook, Inc.

Initial release

2010

2006

2016

2009

under the name LiveDB

2013

Current release

5.10, January 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

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

.NET and C

Python

C++ and CUDA

C++

Server operating systems

.NET

Linux
Unix

Linux

Linux
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

JDBC
ODBC
Thrift
Vega

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

C#
C++
F#
Visual Basic

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/Thrift
Python

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Round robin

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

locking

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.