DBMS > Hypertable vs. OrigoDB vs. RocksDB vs. SiteWhere

System Properties Comparison Hypertable vs. OrigoDB vs. RocksDB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

An open source BigTable implementation based on distributed file systems such as Hadoop

A fully ACID in-memory object graph database

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

M2M integration platform for persisting/querying time series data

Primary database model

Wide column store

Document store
Object oriented DBMS

Key-value store

Time Series DBMS

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

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

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

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

origodb.com

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

origodb.com/docs

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Hypertable Inc.

Robert Friberg et al

Facebook, Inc.

SiteWhere

Initial release

2009

under the name LiveDB

2013

2010

Current release

0.9.8.11, March 2016

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

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++

Java

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

Linux
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

APIs and other access methods

C++ API
Thrift

.NET Client API
HTTP API
LINQ

C++ API
Java API

HTTP REST

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

.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

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

Source-replica replication

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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 authorization

Users with fine-grained authorization concept

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.