DBMS > Graph Engine vs. PouchDB vs. RavenDB vs. SAP HANA

System Properties Comparison Graph Engine vs. PouchDB vs. RavenDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Graph DBMS
Key-value store

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.graphengine.io

pouchdb.com

ravendb.net

www.sap.com/products/hana.html

Technical documentation

www.graphengine.io/docs/manual

pouchdb.com/guides

ravendb.net/docs

help.sap.com/hana

Developer

Microsoft

Apache Software Foundation

Hibernating Rhinos

SAP

Initial release

2010

2012

2010

Current release

7.1.1, June 2019

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

AGPL version 3, commercial license available

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

.NET and C

JavaScript

Server operating systems

.NET

server-less, requires a JavaScript environment (browser, Node.js)

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Data scheme

yes

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

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

View functions in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source 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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Authorization levels configured per client per database

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.