DBMS > Graph Engine vs. Quasardb vs. RRDtool vs. SQLite

System Properties Comparison Graph Engine vs. Quasardb vs. RRDtool vs. SQLite

Please select another system to include it in the comparison.

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

Distributed, high-performance timeseries 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.

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

quasar.ai

oss.oetiker.ch/rrdtool

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

doc.quasar.ai/master

oss.oetiker.ch/rrdtool/doc

www.sqlite.org/docs.html

Developer

Microsoft

quasardb

Tobias Oetiker

Dwayne Richard Hipp

Initial release

2010

2009

1999

2000

Current release

3.14.1, January 2024

1.8.0, 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

GPL V2 and FLOSS

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.

Implementation language

.NET and C

C++

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

Server operating systems

.NET

BSD
Linux
OS X
Windows

HP-UX
Linux

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HTTP API

in-process shared library
Pipes

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

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

via file-system locks

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

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

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.