DBMS > EXASOL vs. Google BigQuery vs. IRONdb vs. Kingbase vs. SiteWhere

System Properties Comparison EXASOL vs. Google BigQuery vs. IRONdb vs. Kingbase vs. SiteWhere

Editorial information provided by DB-Engines

Name

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

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

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

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.exasol.com

cloud.google.com/bigquery

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

www.kingbase.com.cn

github.com/sitewhere/sitewhere

Technical documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

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

sitewhere1.sitewhere.io/index.html

Developer

Exasol

Google

Circonus LLC.

BeiJing KINGBASE Information technologies inc.

SiteWhere

Initial release

2000

2010

2017

1999

2010

Current release

V0.10.20, January 2018

V8.0, August 2021

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.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

C and C++

C and Java

Java

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

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

Standard with numerous extensions

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

HTTP REST

Supported programming languages

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, in Lua

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

ACID

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 rights for users, groups and roles according to SQL-standard

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

Users with fine-grained authorization concept

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.