DBMS > Graphite vs. OrigoDB vs. SAP HANA vs. TerarkDB

System Properties Comparison Graphite vs. OrigoDB vs. SAP HANA vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A fully ACID in-memory object graph database

In-memory, column based data store. Available as appliance or cloud service

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

github.com/graphite-project/graphite-web

origodb.com

www.sap.com/products/hana.html

github.com/bytedance/terarkdb

Technical documentation

graphite.readthedocs.io

origodb.com/docs

help.sap.com/hana

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Chris Davis

Robert Friberg et al

SAP

ByteDance, originally Terark

Initial release

2006

2009

under the name LiveDB

2010

2016

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

C++

Server operating systems

Linux
Unix

Linux
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

Numeric data only

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Sockets

.NET Client API
HTTP API
LINQ

JDBC
ODBC

C++ API
Java API

Supported programming languages

JavaScript (Node.js)
Python

.Net

C++
Java

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

none

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

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 authorization

yes

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.