DBMS > Amazon Redshift vs. PouchDB vs. Transbase vs. VoltDB

System Properties Comparison Amazon Redshift vs. PouchDB vs. Transbase vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

JavaScript DBMS with an API inspired by CouchDB

A resource-optimized, high-performance, universally applicable RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	14.07
Rank	#38	Overall
	#23	Relational DBMS

Score	2.08
Rank	#116	Overall
	#21	Document stores

Score	0.04
Rank	#359	Overall
	#152	Relational DBMS

Score	1.34
Rank	#155	Overall
	#71	Relational DBMS

Website

aws.amazon.com/redshift

pouchdb.com

www.transaction.de/en/products/transbase.html

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

pouchdb.com/guides

www.transaction.de/en/products/transbase/features.html

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Transaction Software GmbH

VoltDB Inc.

Initial release

2012

1987

2010

Current release

7.1.1, June 2019

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

commercial

free development license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C and C++

Java, C++

Server operating systems

hosted

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

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

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

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

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

Multi-source replication
Source-replica replication

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

informational only, not enforced by the system

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Snapshots and command logging

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 and roles with access to stored procedures

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.