DBMS > OrigoDB vs. RRDtool vs. ScyllaDB vs. SQLite

System Properties Comparison OrigoDB vs. RRDtool vs. ScyllaDB vs. SQLite

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.

Cassandra and DynamoDB compatible wide column store

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Object oriented DBMS

Time Series DBMS

Wide column store

Relational DBMS

Secondary database models

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	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

origodb.com

oss.oetiker.ch/rrdtool

www.scylladb.com

www.sqlite.org

Technical documentation

origodb.com/docs

oss.oetiker.ch/rrdtool/doc

docs.scylladb.com

www.sqlite.org/docs.html

Developer

Robert Friberg et al

Tobias Oetiker

ScyllaDB

Dwayne Richard Hipp

Initial release

2009

under the name LiveDB

1999

2015

2000

Current release

1.8.0, 2022

ScyllaDB Open Source 5.4.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

GPL V2 and FLOSS

Open Source

Open Source (AGPL), commercial license available

Open Source

Public Domain

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

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

C++

Server operating systems

Linux
Windows

HP-UX
Linux

Linux

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

User defined using .NET types and collections

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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

cluster global secondary indices

yes

SQL

Support of SQL

SQL-like DML and DDL statements (CQL)

yes

SQL-92 is not fully supported

APIs and other access methods

.NET Client API
HTTP API
LINQ

in-process shared library
Pipes

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

yes, Lua

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

selectable replication factor

Representation of geographical distribution of servers is possible

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

via file-system locks

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

in-memory tables

yes

User concepts

Access control

Role based authorization

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.