DBMS > Google BigQuery vs. NSDb vs. PouchDB vs. Realm vs. Splice Machine

System Properties Comparison Google BigQuery vs. NSDb vs. PouchDB vs. Realm vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

JavaScript DBMS with an API inspired by CouchDB

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

cloud.google.com/bigquery

Technical documentation

cloud.google.com/bigquery/docs

nsdb.io/Architecture

pouchdb.com/guides

realm.io/docs

splicemachine.com/how-it-works

Developer

Google

Apache Software Foundation

Realm, acquired by MongoDB in May 2019

Splice Machine

Initial release

2010

2017

2012

2014

Current release

7.1.1, June 2019

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL 3.0, commercial license available

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, Scala

JavaScript

Java

Server operating systems

hosted

Linux
macOS

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

Android
Backend: server-less
iOS
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

Secondary indexes

all fields are automatically indexed

yes

via views

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC
HTTP REST
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Scala

JavaScript

.Net
Java

with Android only
Objective-C
React Native
Swift

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

runs within the applications so server-side scripts are unnecessary

yes

Java

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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)

Durability

Support for making data persistent

yes

Using Apache Lucene

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

In-Memory realm

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

Access rights for users, groups and roles 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.