DBMS > CouchDB vs. SAP HANA vs. TigerGraph vs. ToroDB vs. XTDB

System Properties Comparison CouchDB vs. SAP HANA vs. TigerGraph vs. ToroDB vs. XTDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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	8.30
Rank	#47	Overall
	#7	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

couchdb.apache.org

www.sap.com/products/hana.html

www.tigergraph.com

github.com/torodb/server

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.couchdb.org/en/stable

help.sap.com/hana

docs.tigergraph.com

www.xtdb.com/docs

Developer

Apache Software Foundation

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

SAP

8Kdata

Juxt Ltd.

Initial release

2005

2010

2017

2016

2019

Current release

3.3.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

AGPL-V3

Open Source

MIT License

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

Java

Clojure

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Linux

All OS with a Java 7 VM

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

yes, extensible-data-notation format

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

SQL-like query language (GSQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

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

C++
Java

Clojure
Java

Server-side scripts

Stored procedures

View functions in JavaScript

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

yes, each node contains all data

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Role-based access control

Access rights for users and 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.