DBMS > Google BigQuery vs. Lovefield vs. PouchDB vs. SQream DB

System Properties Comparison Google BigQuery vs. Lovefield vs. PouchDB vs. SQream DB

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

Embeddable relational database for web apps written in pure JavaScript

JavaScript DBMS with an API inspired by CouchDB

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

cloud.google.com/bigquery

google.github.io/lovefield

pouchdb.com

sqream.com

Technical documentation

cloud.google.com/bigquery/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

pouchdb.com/guides

docs.sqream.com

Developer

Google

Apache Software Foundation

SQream Technologies

Initial release

2010

2014

2012

2017

Current release

2.1.12, February 2017

7.1.1, June 2019

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

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

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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.

Secondary indexes

yes

via views

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

.Net
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

user defined functions in Python

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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

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

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

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.