DBMS > Google BigQuery vs. HarperDB vs. jBASE vs. Postgres-XL

System Properties Comparison Google BigQuery vs. HarperDB vs. jBASE vs. Postgres-XL

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

A robust multi-value DBMS comprising development tools and middleware

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.55
Rank	#252	Overall
	#38	Document stores

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

cloud.google.com/bigquery

www.harperdb.io

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

www.postgres-xl.org

Technical documentation

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

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

www.postgres-xl.org/documentation

Developer

Google

HarperDB

Rocket Software (formerly Zumasys)

Initial release

2010

2017

1991

2014

since 2012, originally named StormDB

Current release

3.1, August 2021

5.7

10 R1, October 2018

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Mozilla public license

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

Node.js

Server operating systems

hosted

Linux
OS X

AIX
Linux
Windows

Linux
macOS

Data scheme

yes

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

Embedded SQL for jBASE in BASIC

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
Basic
Jabbascript
Java

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Custom Functions

since release 3.1

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

yes

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

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic execution of specific operations

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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 and roles

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.