DBMS > Apache Impala vs. Google BigQuery vs. PouchDB vs. Tarantool vs. TimescaleDB

System Properties Comparison Apache Impala vs. Google BigQuery vs. PouchDB vs. Tarantool vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

JavaScript DBMS with an API inspired by CouchDB

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Document store

Spatial DBMS

with Tarantool/GIS extension

Relational DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

impala.apache.org

cloud.google.com/bigquery

pouchdb.com

www.tarantool.io

www.timescale.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

pouchdb.com/guides

www.tarantool.io/en/doc

docs.timescale.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Apache Software Foundation

Timescale

Initial release

2013

2010

2012

2008

2017

Current release

4.1.0, June 2022

7.1.1, June 2019

2.10.0, May 2022

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache 2.0

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

C++

JavaScript

C and C++

Server operating systems

Linux

hosted

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

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL-like DML and DDL statements

yes

Full-featured ANSI SQL support

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

Open binary protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

View functions in JavaScript

Lua, C and SQL stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

Google Cloud Identity & Access Management (IAM)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

fine grained access rights according to SQL-standard

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.