DBMS > Amazon DocumentDB vs. Google BigQuery vs. PouchDB vs. TempoIQ vs. Tibero

System Properties Comparison Amazon DocumentDB vs. Google BigQuery vs. PouchDB vs. TempoIQ vs. Tibero

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service with append-only tables

JavaScript DBMS with an API inspired by CouchDB

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

A secure RDBMS, designed for easy portability from Oracle

Primary database model

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

aws.amazon.com/documentdb

cloud.google.com/bigquery

pouchdb.com

tempoiq.com (offline)

us.tmaxsoft.com/products/tibero

Technical documentation

aws.amazon.com/documentdb/resources

cloud.google.com/bigquery/docs

pouchdb.com/guides

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

Developer

Google

Apache Software Foundation

TempoIQ

TmaxSoft

Initial release

2019

2010

2012

2003

Current release

7.1.1, June 2019

6, April 2015

License

Commercial or Open Source

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

JavaScript

C and Assembler

Server operating systems

hosted

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

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

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

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

C#
Java
JavaScript

Node.js
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

Persistent Stored Procedure (PSM)

Triggers

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

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

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

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

planned for next version

User concepts

Access control

Access rights for users and roles

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

simple authentication-based access control

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.