DBMS > Apache Impala vs. GeoSpock vs. IBM Cloudant vs. MaxDB vs. SAP HANA

System Properties Comparison Apache Impala vs. GeoSpock vs. IBM Cloudant vs. MaxDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Analytic DBMS for Hadoop

Spatial and temporal data processing engine for extreme data scale

Database as a Service offering based on Apache CouchDB

A robust and reliable RDBMS optimized to run all major SAP solutions

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

impala.apache.org

geospock.com

www.ibm.com/products/cloudant

maxdb.sap.com

www.sap.com/products/hana.html

Technical documentation

impala.apache.org/impala-docs.html

cloud.ibm.com/docs/Cloudant

maxdb.sap.com/documentation

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

GeoSpock

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP, acquired from Software AG (Adabas-D) in 1997

SAP

Initial release

2013

2010

1984

2010

Current release

4.1.0, June 2022

2.0, September 2019

7.9.10.12, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Limited community edition free

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java, Javascript

Erlang

C++

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC
ODBC

JDBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
WebDAV

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions (Map-Reduce) in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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 can be defined per table

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

yes

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.