DBMS > BoltDB vs. Cachelot.io vs. Google Cloud Datastore vs. Postgres-XL vs. RocksDB

System Properties Comparison BoltDB vs. Cachelot.io vs. Google Cloud Datastore vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

In-memory caching system

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.00
Rank	#396	Overall
	#64	Key-value stores

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

cachelot.io

cloud.google.com/datastore

www.postgres-xl.org

rocksdb.org

Technical documentation

cloud.google.com/datastore/docs

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

Google

Facebook, Inc.

Initial release

2013

2015

2008

2014

since 2012, originally named StormDB

2013

Current release

10 R1, October 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Simplified BSD License

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++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

hosted

Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

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 (GQL)

yes

distributed, parallel query execution

APIs and other access methods

Memcached protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.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

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.