DBMS > Lovefield vs. Postgres-XL vs. RocksDB vs. RRDtool

System Properties Comparison Lovefield vs. Postgres-XL vs. RocksDB vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

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.

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

google.github.io/lovefield

www.postgres-xl.org

rocksdb.org

oss.oetiker.ch/rrdtool

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

Google

Facebook, Inc.

Tobias Oetiker

Initial release

2014

since 2012, originally named StormDB

2013

1999

Current release

2.1.12, February 2017

10 R1, October 2018

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Mozilla public license

Open Source

BSD

Open Source

GPL V2 and FLOSS

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

JavaScript

C++

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

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS

Linux

HP-UX
Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

yes

XML type, but no XML query functionality

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

distributed, parallel query execution

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

JavaScript

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights 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.