DBMS > CouchDB vs. Google BigQuery vs. Percona Server for MongoDB vs. Prometheus

System Properties Comparison CouchDB vs. Google BigQuery vs. Percona Server for MongoDB vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

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

Open-source Time Series DBMS and monitoring system

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

couchdb.apache.org

cloud.google.com/bigquery

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

prometheus.io

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

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

prometheus.io/docs

Developer

Apache Software Foundation

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

Google

Percona

Initial release

2005

2010

2015

Current release

3.3.3, December 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

GPL Version 2

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

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

proprietary protocol using JSON

RESTful HTTP/JSON API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

in JavaScript

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

Since BigQuery is designed for querying data

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 can be defined per database

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for 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.