DBMS > Amazon Redshift vs. Graph Engine vs. PlanetScale vs. PouchDB vs. searchxml

System Properties Comparison Amazon Redshift vs. Graph Engine vs. PlanetScale vs. PouchDB vs. searchxml

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

JavaScript DBMS with an API inspired by CouchDB

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Document store

Native XML DBMS
Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

aws.amazon.com/redshift

www.graphengine.io

planetscale.com

pouchdb.com

www.searchxml.net/category/products

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

planetscale.com/docs

pouchdb.com/guides

www.searchxml.net/support/handouts

Developer

Amazon (based on PostgreSQL)

Microsoft

PlanetScale

Apache Software Foundation

informationpartners gmbh

Initial release

2012

2010

2020

2012

2015

Current release

7.1.1, June 2019

1.0

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

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

.NET and C

JavaScript

C++

Server operating systems

hosted

.NET

Docker
Linux
macOS

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

Windows

Data scheme

yes

schema-free

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

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

View functions in JavaScript

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

sychronisation to multiple collections

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 across shards
Immediate Consistency within a shard

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.