DBMS > Apache Impala vs. EXASOL vs. Google BigQuery vs. Hazelcast vs. Rockset

System Properties Comparison Apache Impala vs. EXASOL vs. Google BigQuery vs. Hazelcast vs. Rockset

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

Relational DBMS
Search engine

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

impala.apache.org

www.exasol.com

cloud.google.com/bigquery

hazelcast.com

rockset.com

Technical documentation

impala.apache.org/impala-docs.html

www.exasol.com/resources

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

docs.rockset.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Exasol

Google

Hazelcast

Rockset

Initial release

2013

2000

2010

2008

2019

Current release

4.1.0, June 2022

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; commercial licenses 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

C++

Java

C++

Server operating systems

Linux

hosted

All OS with a Java VM

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

the object must implement a serialization strategy

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Replicated Map

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual 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

one or two-phase-commit; repeatable reads; read commited

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

based on Apache Sentry and Kerberos

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)

Role-based access control

Access rights for users and organizations can be defined via Rockset console

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.