DBMS > CouchDB vs. Google Cloud Datastore vs. InfinityDB vs. MySQL vs. searchxml

System Properties Comparison CouchDB vs. Google Cloud Datastore vs. InfinityDB vs. MySQL vs. searchxml

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.

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

A Java embedded Key-Value Store which extends the Java Map interface

Widely used open source RDBMS

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

couchdb.apache.org

cloud.google.com/datastore

boilerbay.com

www.mysql.com

www.searchxml.net/category/products

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

boilerbay.com/infinitydb/manual

dev.mysql.com/doc

www.searchxml.net/support/handouts

Developer

Apache Software Foundation

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

Google

Boiler Bay Inc.

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Initial release

2005

2008

2002

1995

2015

Current release

3.3.3, December 2023

4.0

8.4.0, April 2024

1.0

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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 MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Erlang

Java

C and C++

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

via views

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

View functions in JavaScript

using Google App Engine

yes

proprietary syntax

yes

on the application server

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

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

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

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

Optimistic locking for transactions; no isolation for bulk loads

ACID

not for MyISAM storage engine

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

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

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

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.