DBMS > Google BigQuery vs. Graph Engine vs. jBASE vs. Microsoft Azure SQL Database vs. PouchDB

System Properties Comparison Google BigQuery vs. Graph Engine vs. jBASE vs. Microsoft Azure SQL Database vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A robust multi-value DBMS comprising development tools and middleware

Database as a Service offering with high compatibility to Microsoft SQL Server

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Multivalue DBMS

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

cloud.google.com/bigquery

www.graphengine.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

azure.microsoft.com/en-us/products/azure-sql/database

pouchdb.com

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.microsoft.com/en-us/azure/azure-sql

pouchdb.com/guides

Developer

Google

Microsoft

Rocket Software (formerly Zumasys)

Microsoft

Apache Software Foundation

Initial release

2010

1991

2010

2012

Current release

5.7

V12

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

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

.NET and C

C++

JavaScript

Server operating systems

hosted

.NET

AIX
Linux
Windows

hosted

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

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
Basic
Jabbascript
Java

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Transact SQL

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 can be defined down to the item level

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.