DBMS > CouchDB vs. Oracle Coherence vs. SAP HANA vs. Vitess

System Properties Comparison CouchDB vs. Oracle Coherence vs. SAP HANA vs. Vitess

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.

Oracles in-memory data grid solution

In-memory, column based data store. Available as appliance or cloud service

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS

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

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	1.90
Rank	#127	Overall
	#21	Key-value stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

couchdb.apache.org

www.oracle.com/java/coherence

www.sap.com/products/hana.html

vitess.io

Technical documentation

docs.couchdb.org/en/stable

docs.oracle.com/en/middleware/standalone/coherence

help.sap.com/hana

vitess.io/docs

Developer

Apache Software Foundation

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

Oracle

SAP

The Linux Foundation, PlanetScale

Initial release

2005

2007

2010

2013

Current release

3.3.3, December 2023

14.1, August 2023

2.0 SPS07 (April 4, 2023), April 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Appliance or cloud-service

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
C++
Java

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

Server-side scripts

Stored procedures

View functions in JavaScript

SQLScript, R

yes

proprietary syntax

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, with selectable consistency level

yes

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

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

configurable

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optionally

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

authentification to access the cache via certificates or http basic authentication

yes

Users with fine-grained authorization concept

no user groups or 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.