DBMS > Google BigQuery vs. HyperSQL vs. Riak TS vs. searchxml

System Properties Comparison Google BigQuery vs. HyperSQL vs. Riak TS vs. searchxml

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Time Series DBMS

Native XML DBMS
Search engine

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

cloud.google.com/bigquery

hsqldb.org

www.searchxml.net/category/products

Technical documentation

cloud.google.com/bigquery/docs

hsqldb.org/web/hsqlDocsFrame.html

www.tiot.jp/riak-docs/riak/ts/latest

www.searchxml.net/support/handouts

Developer

Google

Open Source, formerly Basho Technologies

informationpartners gmbh

Initial release

2010

2001

2015

Current release

2.7.2, June 2023

3.0.0, September 2022

1.0

License

Commercial or Open Source

commercial

Open Source

based on BSD license

Open Source

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

Erlang

C++

Server operating systems

hosted

All OS with a Java VM

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

Linux
OS X

Windows

Data scheme

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.

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

JDBC via HTTP
JDBC
ODBC

HTTP API
Native Erlang Interface

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

Erlang

yes

on the application server

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

multiple readers, single writer

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

Domain, group and role-based access control at the document level and for application services

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.