DBMS > Couchbase vs. Datomic vs. Google Cloud Datastore vs. KairosDB

System Properties Comparison Couchbase vs. Datomic vs. Google Cloud Datastore vs. KairosDB

Please select another system to include it in the comparison.

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

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	18.46
Rank	#36	Overall
	#5	Document stores

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Website

www.couchbase.com

www.datomic.com

cloud.google.com/datastore

github.com/kairosdb/kairosdb

Technical documentation

docs.couchbase.com

docs.datomic.com

cloud.google.com/datastore/docs

kairosdb.github.io

Developer

Couchbase, Inc.

Cognitect

Google

Initial release

2011

2012

2008

2013

Current release

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

1.0.6735, June 2023

1.2.2, November 2018

License

Commercial or Open Source

Open Source

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

commercial

limited edition free

commercial

Open Source

Apache 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

Java, Clojure

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

hosted

Linux
OS X
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (GQL)

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

RESTful HTTP API

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

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Clojure
Java

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

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

yes

Transaction Functions

using Google App Engine

Triggers

yes

via the TAP protocol

By using transaction functions

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

But extensive use of caching in the application peers

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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

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.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

recommended only for testing and development

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)

simple password-based access control

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.