DBMS > CouchDB vs. EXASOL vs. Machbase Neo vs. OrientDB vs. Snowflake

System Properties Comparison CouchDB vs. EXASOL vs. Machbase Neo vs. OrientDB vs. Snowflake

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.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

TimeSeries DBMS for AIoT and BigData

Multi-model DBMS (Document, Graph, Key/Value)

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.couchdb.org/en/stable

www.exasol.com/resources

machbase.com/dbms

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

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

Exasol

Machbase

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2005

2000

2013

2010

2014

Current release

3.3.3, December 2023

V8.0, August 2023

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

free test version available

Open Source

Apache version 2

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.

Implementation language

Erlang

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

All OS with a Java JDK (>= JDK 6)

hosted

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language, no joins

yes

APIs and other access methods

RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Java, Javascript

user defined functions

Triggers

yes

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

volatile and lookup table

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles according to SQL-standard

simple password-based access control

Access rights for users and roles; record level security configurable

Users with fine-grained authorization concept, user roles and pluggable authentication

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.