DBMS > Cachelot.io vs. Newts vs. PlanetScale vs. Postgres-XL vs. RocksDB

System Properties Comparison Cachelot.io vs. Newts vs. PlanetScale vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

Time Series DBMS based on Cassandra

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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.04
Rank	#388	Overall
	#62	Key-value stores

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

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

Website

cachelot.io

opennms.github.io/newts

planetscale.com

www.postgres-xl.org

rocksdb.org

Technical documentation

github.com/OpenNMS/newts/wiki

planetscale.com/docs

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

OpenNMS Group

PlanetScale

Facebook, Inc.

Initial release

2015

2014

2020

2014

since 2012, originally named StormDB

2013

Current release

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache 2.0

commercial

Open Source

Mozilla public license

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Windows

Docker
Linux
macOS

Linux
macOS

Linux

Data scheme

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

yes

with proprietary extensions

yes

distributed, parallel query execution

APIs and other access methods

Memcached protocol

HTTP REST
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

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

C++ API
Java API

Supported programming languages

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

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.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

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

Users with fine-grained authorization concept

no user groups or roles

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.