DBMS > Google BigQuery vs. HyperSQL vs. IRONdb vs. Linter

System Properties Comparison Google BigQuery vs. HyperSQL vs. IRONdb vs. Linter

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service with append-only tables

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

RDBMS for high security requirements

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial 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.09
Rank	#346	Overall
	#152	Relational DBMS

Website

cloud.google.com/bigquery

hsqldb.org

www.circonus.com/solutions/time-series-database/

linter.ru

Technical documentation

cloud.google.com/bigquery/docs

hsqldb.org/web/hsqlDocsFrame.html

docs.circonus.com/irondb/category/getting-started

Developer

Google

Circonus LLC.

relex.ru

Initial release

2010

2001

2017

1990

Current release

2.7.2, June 2023

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

based on BSD license

commercial

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

Server operating systems

hosted

All OS with a Java VM

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

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

JDBC via HTTP
JDBC
ODBC

HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

yes, in Lua

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

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

Immediate consistency per node, eventual consistency across nodes

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

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

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.