DBMS > Apache Impala vs. GridGain vs. Microsoft SQL Server vs. RavenDB vs. SWC-DB

System Properties Comparison Apache Impala vs. GridGain vs. Microsoft SQL Server vs. RavenDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store

Wide column store

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Website

impala.apache.org

www.gridgain.com

www.microsoft.com/en-us/sql-server

ravendb.net

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

impala.apache.org/impala-docs.html

www.gridgain.com/docs/index.html

learn.microsoft.com/en-US/sql/sql-server

ravendb.net/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

GridGain Systems, Inc.

Microsoft

Hibernating Rhinos

Alex Kashirin

Initial release

2013

2007

1989

2010

2020

Current release

4.1.0, June 2022

GridGain 8.5.1

SQL Server 2022, November 2022

5.4, July 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java, C++, .Net

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

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

yes

SQL-like query language (RQL)

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Proprietary protocol
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.