DBMS > Google BigQuery vs. Heroic vs. HyperSQL vs. Microsoft Azure Synapse Analytics vs. Warp 10

System Properties Comparison Google BigQuery vs. Heroic vs. HyperSQL vs. Microsoft Azure Synapse Analytics vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	3.90
Rank	#85	Overall
	#46	Relational DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

cloud.google.com/bigquery

github.com/spotify/heroic

hsqldb.org

azure.microsoft.com/services/synapse-analytics

www.warp10.io

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

hsqldb.org/web/hsqlDocsFrame.html

docs.microsoft.com/azure/synapse-analytics

www.warp10.io/content/02_Getting_started

Developer

Google

Spotify

Microsoft

SenX

Initial release

2010

2014

2001

2016

2015

Current release

2.7.2, June 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

based on BSD license

commercial

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

All OS with a Java VM

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

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

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

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

C#
Java
PHP

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

Transact SQL

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

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

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.