DBMS > BoltDB vs. Google Cloud Datastore vs. IBM Db2 vs. Oracle Rdb vs. RocksDB

System Properties Comparison BoltDB vs. Google Cloud Datastore vs. IBM Db2 vs. Oracle Rdb vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

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

Primary database model

Key-value store

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Key-value store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

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

Website

github.com/boltdb/bolt

cloud.google.com/datastore

www.ibm.com/products/db2

www.oracle.com/database/technologies/related/rdb.html

rocksdb.org

Technical documentation

cloud.google.com/datastore/docs

www.ibm.com/docs/en/db2

www.oracle.com/database/technologies/related/rdb-doc.html

github.com/facebook/rocksdb/wiki

Developer

Google

IBM

Oracle, originally developed by Digital Equipment Corporation (DEC)

Facebook, Inc.

Initial release

2013

2008

1983

host version

1984

2013

Current release

12.1, October 2016

7.4.1.1, 2021

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

free version is available

commercial

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

HP Open VMS

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

C++ API
Java API

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

with separate tools (MQ, InfoSphere)

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

yes, on a single node

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.