DBMS > Couchbase vs. GBase vs. Google Cloud Datastore vs. Ignite vs. Tkrzw

System Properties Comparison Couchbase vs. GBase vs. Google Cloud Datastore vs. Ignite vs. Tkrzw

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store

Relational DBMS

Document store

Key-value store
Relational DBMS

Key-value store

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

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.couchbase.com

www.gbase.cn

cloud.google.com/datastore

ignite.apache.org

dbmx.net/tkrzw

Technical documentation

docs.couchbase.com

cloud.google.com/datastore/docs

apacheignite.readme.io/docs

Developer

Couchbase, Inc.

General Data Technology Co., Ltd.

Google

Apache Software Foundation

Mikio Hirabayashi

Initial release

2011

2004

2008

2015

2020

Current release

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

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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

C, Java, Python

C++, Java, .Net

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

Standard with numerous extensions

SQL-like query language (GQL)

ANSI-99 for query and DML statements, subset of DDL

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

ADO.NET
C API
JDBC
ODBC

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

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

user defined functions

using Google App Engine

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

via the TAP protocol

yes

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

Multi-source replication using Paxos

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

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

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

Ephemeral buckets

yes

using specific database classes

User concepts

Access control

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

yes

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

Security Hooks for custom implementations

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.