DBMS > CouchDB vs. Dolt vs. Infobright vs. SAP HANA

System Properties Comparison CouchDB vs. Dolt vs. Infobright vs. SAP HANA

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.

A MySQL compatible DBMS with Git-like versioning of data and schema

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

github.com/dolthub/dolt
www.dolthub.com

ignitetech.com/softwarelibrary/infobrightdb

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

docs.dolthub.com

help.sap.com/hana

Developer

Apache Software Foundation

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

DoltHub Inc

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP

Initial release

2005

2018

2005

2010

Current release

3.3.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
Windows

Appliance or cloud-service

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

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

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

yes

currently in alpha release

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

yes

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

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes

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.