DBMS > CouchDB vs. Graph Engine vs. Ingres vs. SAP HANA vs. YDB

System Properties Comparison CouchDB vs. Graph Engine vs. Ingres vs. SAP HANA vs. YDB

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Well established RDBMS

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

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store

Graph DBMS
Key-value store

Relational DBMS

Document store
Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

couchdb.apache.org

www.graphengine.io

www.actian.com/databases/ingres

www.sap.com/products/hana.html

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.couchdb.org/en/stable

www.graphengine.io/docs/manual

docs.actian.com/ingres

help.sap.com/hana

ydb.tech/en/docs

Developer

Apache Software Foundation

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

Microsoft

Actian Corporation

SAP

Yandex

Initial release

2005

2010

1974

originally developed at University Berkely in early 1970s

2010

2019

Current release

3.3.3, December 2023

11.2, May 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

MIT License

commercial

Open Source

Apache 2.0; commercial license 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

.NET and C

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

.NET

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

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

C#
C++
F#
Visual Basic

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Ingres Replicator

yes

Active-passive shard 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

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

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

MVCC

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

Access rights defined for Yandex Cloud users

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.