DBMS > Apache Impala vs. Google BigQuery vs. GridGain vs. MySQL vs. SAP SQL Anywhere

System Properties Comparison Apache Impala vs. Google BigQuery vs. GridGain vs. MySQL vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used open source RDBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Website

impala.apache.org

cloud.google.com/bigquery

www.gridgain.com

www.mysql.com

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

dev.mysql.com/doc

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

GridGain Systems, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Initial release

2013

2010

2007

1995

1992

Current release

4.1.0, June 2022

GridGain 8.5.1

9.0.0, July 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

commercial, open source

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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++, .Net, Python, REST, SQL

C and C++

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.