DBMS > Google BigQuery vs. HyperSQL vs. JaguarDB vs. Microsoft Azure Table Storage vs. Transbase

System Properties Comparison Google BigQuery vs. HyperSQL vs. JaguarDB vs. Microsoft Azure Table Storage vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Wide column store

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/bigquery

hsqldb.org

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

hsqldb.org/web/hsqlDocsFrame.html

www.jaguardb.com/support.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

DataJaguar, Inc.

Microsoft

Transaction Software GmbH

Initial release

2010

2001

2015

2012

1987

Current release

2.7.2, June 2023

3.3 July 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

based on BSD license

Open Source

GPL V3.0

commercial

free development 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

Java

C++

the server part. Clients available in other languages

C and C++

Server operating systems

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

JDBC via HTTP
JDBC
ODBC

JDBC
ODBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

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

optimistic locking

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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)

fine grained access rights according to SQL-standard

rights management via user accounts

Access rights based on private key authentication or shared access signatures

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.