DBMS > Amazon Redshift vs. Dgraph vs. EJDB vs. PouchDB vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Dgraph vs. EJDB vs. PouchDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

JavaScript DBMS with an API inspired by CouchDB

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

dgraph.io

github.com/Softmotions/ejdb

pouchdb.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

github.com/Softmotions/ejdb/blob/master/README.md

pouchdb.com/guides

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Softmotions

Apache Software Foundation

DataChemist Ltd.

Initial release

2012

2016

2012

2018

Current release

7.1.1, June 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPLv2

Open Source

GPL V3

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

JavaScript

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Windows

server-less

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

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

in-process shared library

HTTP REST

only for PouchDB Server
JavaScript API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

JavaScript

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Journaling Streams

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Planned for future releases

Role-based access control

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.