DBMS > Coveo vs. PouchDB vs. RethinkDB vs. SAP HANA vs. SwayDB

System Properties Comparison Coveo vs. PouchDB vs. RethinkDB vs. SAP HANA vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

JavaScript DBMS with an API inspired by CouchDB

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Spatial 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	2.14
Rank	#116	Overall
	#11	Search engines

Score	2.18
Rank	#114	Overall
	#21	Document stores

Score	2.58
Rank	#105	Overall
	#20	Document stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.00
Rank	#384	Overall
	#60	Key-value stores

Website

www.coveo.com

pouchdb.com

rethinkdb.com

www.sap.com/products/hana.html

swaydb.simer.au

Technical documentation

Developer

Coveo

Apache Software Foundation

The Linux Foundation

since July 2017

SAP

Simer Plaha

Initial release

2012

2009

2010

2018

Current release

7.1.1, June 2019

2.4.1, August 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

GNU Affero GPL V3.0

Cloud-based only

Only available as a cloud service

yes

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

JavaScript

C++

Scala

Server operating systems

hosted

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

Linux
OS X
Windows

Appliance or cloud-service

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

yes

APIs and other access methods

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

JavaScript

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Java
Kotlin
Scala

Server-side scripts

Stored procedures

View functions in JavaScript

SQLScript, R

Triggers

yes

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

range based

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic single-document operations

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

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

granular access controls, API key management, content filters

yes

users and table-level permissions

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.