DBMS > Google BigQuery vs. Heroic vs. Kinetica vs. OpenQM vs. searchxml

System Properties Comparison Google BigQuery vs. Heroic vs. Kinetica vs. OpenQM vs. searchxml

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

Fully vectorized database across both GPUs and CPUs

QpenQM is a high-performance, self-tuning, multi-value DBMS

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

cloud.google.com/bigquery

github.com/spotify/heroic

www.kinetica.com

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

www.searchxml.net/category/products

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

docs.kinetica.com

www.searchxml.net/support/handouts

Developer

Google

Spotify

Kinetica

Rocket Software, originally Martin Phillips

informationpartners gmbh

Initial release

2010

2014

2012

1993

2015

Current release

7.1, August 2021

3.4-12

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPLv2, extended commercial license available

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

C++

Server operating systems

hosted

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Windows

Data scheme

yes

schema-free

yes

with some exceptions

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

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

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

.Net
Basic
C
Java
Objective C
PHP
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

on the application server

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

sychronisation to multiple collections

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 or Eventual Consistency depending on configuration

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

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

GPU vRAM or System RAM

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 on table level

Access rights can be defined down to the item level

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.