DBMS > ClickHouse vs. CouchDB vs. Google Cloud Datastore vs. ObjectBox vs. Percona Server for MongoDB

System Properties Comparison ClickHouse vs. CouchDB vs. Google Cloud Datastore vs. ObjectBox vs. Percona Server for MongoDB

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Extremely fast embedded database for small devices, IoT and Mobile

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Secondary database models

Time Series DBMS

Spatial DBMS

using the Geocouch extension

Time Series DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

clickhouse.com

couchdb.apache.org

cloud.google.com/datastore

objectbox.io

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

clickhouse.com/docs

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

docs.objectbox.io

docs.percona.com/percona-distribution-for-mongodb

Developer

Clickhouse Inc.

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

ObjectBox Limited

Percona

Initial release

2016

2005

2008

2017

2015

Current release

v24.4.1.2088-stable, May 2024

3.3.3, December 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

commercial

Open Source

Apache License 2.0

Open Source

GPL Version 2

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

C++

Erlang

C and C++

C++

Server operating systems

FreeBSD
Linux
macOS

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Android
iOS
Linux
macOS
Windows

Linux

Data scheme

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

RESTful HTTP/JSON API

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

Proprietary native API

proprietary protocol using JSON

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes

View functions in JavaScript

using Google App Engine

JavaScript

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

improved architecture with release 2.0

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

online/offline synchronization between client and server

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Eventual Consistency
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

atomic operations within a single document possible

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

via In-Memory Engine

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users can be defined per database

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

yes

Access rights for users and roles

More information provided by the system vendor

News

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

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.