DBMS > Lovefield vs. Memcached vs. Newts vs. Postgres-XL vs. RocksDB

System Properties Comparison Lovefield vs. Memcached vs. Newts vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

In-memory key-value store, originally intended for caching

Time Series DBMS based on Cassandra

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

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

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

Website

google.github.io/lovefield

www.memcached.org

opennms.github.io/newts

www.postgres-xl.org

rocksdb.org

Technical documentation

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

github.com/memcached/memcached/wiki

github.com/OpenNMS/newts/wiki

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

OpenNMS Group

Facebook, Inc.

Initial release

2014

2003

2014

since 2012, originally named StormDB

2013

Current release

2.1.12, February 2017

1.6.25, March 2024

10 R1, October 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD license

Open Source

Apache 2.0

Open Source

Mozilla public license

Open Source

BSD

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

Java

C++

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X
Windows

Linux
macOS

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

yes

XML type, but no XML query functionality

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

Proprietary protocol

HTTP REST
Java API

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

C++ API
Java API

Supported programming languages

JavaScript

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Java

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

C
C++
Go
Java
Perl
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

Sharding

based on Cassandra

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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.