DBMS > Apache Impala vs. Google BigQuery vs. H2GIS vs. ScyllaDB

System Properties Comparison Apache Impala vs. Google BigQuery vs. H2GIS vs. ScyllaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

Spatial extension of H2

Cassandra and DynamoDB compatible wide column store

Primary database model

Relational DBMS

Spatial DBMS

Wide column store

Secondary database models

Document store

Relational DBMS

Key-value store

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	4.15
Rank	#69	Overall
	#5	Wide column stores

Website

impala.apache.org

cloud.google.com/bigquery

www.h2gis.org

www.scylladb.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

www.h2gis.org/docs/home

docs.scylladb.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

CNRS

ScyllaDB

Initial release

2013

2010

2013

2015

Current release

4.1.0, June 2022

ScyllaDB Open Source 6.0.2, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

LGPL 3.0

Open Source

Open Source (AGPL), commercial license available

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Java

C++

Server operating systems

Linux

hosted

Linux

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.

Secondary indexes

yes

cluster global secondary indices

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like DML and DDL statements (CQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes

based on H2

yes, Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

based on H2

selectable replication factor

Representation of geographical distribution of servers is possible

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

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

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

in-memory tables

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

based on H2

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.