DBMS > Couchbase vs. Google Cloud Bigtable vs. Oracle NoSQL vs. SpaceTime vs. Tarantool

System Properties Comparison Couchbase vs. Google Cloud Bigtable vs. Oracle NoSQL vs. SpaceTime vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

SpaceTime is a spatio-temporal DBMS with a focus on performance.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Spatial DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.couchbase.com

cloud.google.com/bigtable

www.oracle.com/database/nosql/technologies/nosql

www.mireo.com/spacetime

www.tarantool.io

Technical documentation

docs.couchbase.com

cloud.google.com/bigtable/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.tarantool.io/en/doc

Developer

Couchbase, Inc.

Google

Oracle

Mireo

Initial release

2011

2015

2011

2020

2008

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

24.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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, C++, Go and Erlang

Java

C++

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
Solaris SPARC/x86

Linux

BSD
Linux
macOS

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

optional

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

Full-featured ANSI SQL support

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

RESTful HTTP API

Open binary protocol

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
Go
Java
JavaScript (Node.js)
Python

C#
C++
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Lua, C and SQL stored procedures

Triggers

yes

via the TAP protocol

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

Fixed-grid hypercubes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Real-time block device replication (DRBD)

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

configurable

ACID within a storage node (=shard)

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

Ephemeral buckets

yes

off heap cache

yes, full featured in-memory storage engine with persistence

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

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

Access rights for users and roles

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.