DBMS > Google BigQuery vs. jBASE vs. Postgres-XL vs. Realm vs. VoltDB

System Properties Comparison Google BigQuery vs. jBASE vs. Postgres-XL vs. Realm vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A robust multi-value DBMS comprising development tools and middleware

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

cloud.google.com/bigquery

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

www.postgres-xl.org

realm.io

www.voltdb.com

Technical documentation

cloud.google.com/bigquery/docs

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

www.postgres-xl.org/documentation

realm.io/docs

docs.voltdb.com

Developer

Google

Rocket Software (formerly Zumasys)

Realm, acquired by MongoDB in May 2019

VoltDB Inc.

Initial release

2010

1991

2014

since 2012, originally named StormDB

2014

2010

Current release

5.7

10 R1, October 2018

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

hosted

AIX
Linux
Windows

Linux
macOS

Android
Backend: server-less
iOS
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

yes

distributed, parallel query execution

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions

runs within the applications so server-side scripts are unnecessary

Java

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

MVCC

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

In-Memory realm

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

yes

Users and roles with access to stored procedures

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.