DBMS > Amazon Redshift vs. Datomic vs. PouchDB vs. Tibero

System Properties Comparison Amazon Redshift vs. Datomic vs. PouchDB vs. Tibero

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

JavaScript DBMS with an API inspired by CouchDB

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

aws.amazon.com/redshift

www.datomic.com

pouchdb.com

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

pouchdb.com/guides

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon (based on PostgreSQL)

Cognitect

Apache Software Foundation

TmaxSoft

Initial release

2012

2003

Current release

1.0.6735, June 2023

7.1.1, June 2019

6, April 2015

License

Commercial or Open Source

commercial

limited edition free

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

Java, Clojure

JavaScript

C and Assembler

Server operating systems

hosted

All OS with a Java VM

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

AIX
HP-UX
Linux
Solaris
Windows

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.

yes

Secondary indexes

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

JavaScript

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

View functions in JavaScript

Persistent Stored Procedure (PSM)

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.