DBMS > CouchDB vs. EsgynDB vs. Google BigQuery vs. HBase

System Properties Comparison CouchDB vs. EsgynDB vs. Google BigQuery vs. HBase

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Large scale data warehouse service with append-only tables

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

Document store

Relational DBMS

Wide column store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Website

couchdb.apache.org

www.esgyn.cn

cloud.google.com/bigquery

hbase.apache.org

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

Developer

Apache Software Foundation

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

Esgyn

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2005

2015

2010

2008

Current release

3.3.3, December 2023

2.3.4, January 2021

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache 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.

Implementation language

Erlang

C++, Java

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux

hosted

Linux
Unix
Windows

using Cygwin

Data scheme

schema-free

yes

schema-free, schema definition possible

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

View functions in JavaScript

Java Stored Procedures

user defined functions

in JavaScript

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

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

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Since BigQuery is designed for querying data

Single row ACID (across millions of columns)

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

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.