DBMS > OrigoDB vs. RRDtool vs. Splice Machine vs. TerarkDB

System Properties Comparison OrigoDB vs. RRDtool vs. Splice Machine vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

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

Document store
Object oriented DBMS

Time Series DBMS

Relational DBMS

Key-value store

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	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

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

Website

origodb.com

oss.oetiker.ch/rrdtool

splicemachine.com

github.com/bytedance/terarkdb

Technical documentation

origodb.com/docs

oss.oetiker.ch/rrdtool/doc

splicemachine.com/how-it-works

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Robert Friberg et al

Tobias Oetiker

Splice Machine

ByteDance, originally Terark

Initial release

2009

under the name LiveDB

1999

2014

2016

Current release

1.8.0, 2022

3.1, March 2021

License

Commercial or Open Source

Open Source

GPL V2 and FLOSS

Open Source

AGPL 3.0, commercial license available

commercial

restricted open source version available

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

Implementations in Java (e.g. RRD4J) and C# available

Java

C++

Server operating systems

Linux
Windows

HP-UX
Linux

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

in-process shared library
Pipes

JDBC
Native Spark Datasource
ODBC

C++ API
Java API

Supported programming languages

.Net

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

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

by using the rrdcached daemon

yes, multi-version concurrency control (MVCC)

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

Access rights for users, groups and roles 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Cacti servers under attack by attackers exploiting CVE-2022-46169
16 January 2023, Help Net Security

Critical IP spoofing bug patched in Cacti
15 December 2022, The Daily Swig

How to install Cacti SNMP Monitor on Ubuntu
24 November 2017, TechRepublic

Installation Guide for Collectd and Collectd-Web to Monitor Server Resources in Linux
29 November 2017, Linux.com

SNMP: The Little Protocol That Could
7 November 2020, Techopedia

provided by Google News

Machine learning data pipeline outfit Splice Machine files for insolvency
26 August 2021, The Register

Splice Machine Launches the Splice Machine Feature Store to Simplify Feature Engineering and Democratize Machine ...
19 January 2021, PR Newswire

Splice Machine Launches Feature Store to Simplify Feature Engineering
19 January 2021, Datanami

How Splice Machine's Data Platform for Intelligent Apps Works
29 September 2020, eWeek

Distributed SQL System Review: Snowflake vs Splice Machine
18 September 2019, Towards Data Science

provided by Google News

Share this page