DBMS > CouchDB vs. EventStoreDB vs. SAP HANA vs. Sphinx vs. YDB

System Properties Comparison CouchDB vs. EventStoreDB vs. SAP HANA vs. Sphinx 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.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Open source search engine for searching in data from different sources, e.g. relational databases

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
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	1.10
Rank	#179	Overall
	#1	Event Stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

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

Website

couchdb.apache.org

www.eventstore.com

www.sap.com/products/hana.html

sphinxsearch.com

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

Technical documentation

docs.couchdb.org/en/stable

developers.eventstore.com

help.sap.com/hana

sphinxsearch.com/docs

ydb.tech/en/docs

Developer

Apache Software Foundation

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

Event Store Limited

SAP

Sphinx Technologies Inc.

Yandex

Initial release

2005

2012

2010

2001

2019

Current release

3.3.3, December 2023

21.2, February 2021

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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.

Secondary indexes

yes

via views

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

View functions in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

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

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

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.