DBMS > Google BigQuery vs. PouchDB vs. Splice Machine vs. Teradata

System Properties Comparison Google BigQuery vs. PouchDB vs. Splice Machine vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

JavaScript DBMS with an API inspired by CouchDB

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

cloud.google.com/bigquery

pouchdb.com

splicemachine.com

www.teradata.com

Technical documentation

cloud.google.com/bigquery/docs

pouchdb.com/guides

splicemachine.com/how-it-works

docs.teradata.com

Developer

Google

Apache Software Foundation

Splice Machine

Teradata

Initial release

2010

2012

2014

1984

Current release

7.1.1, June 2019

3.1, March 2021

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

AGPL 3.0, commercial license available

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

Java

Server operating systems

hosted

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

Linux
OS X
Solaris
Windows

hosted
Linux

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

yes

via views

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
Native Spark Datasource
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

yes

Java

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

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

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

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.