DBMS > Apache Impala vs. Atos Standard Common Repository vs. CouchDB vs. Microsoft Azure AI Search vs. SAP HANA

System Properties Comparison Apache Impala vs. Atos Standard Common Repository vs. CouchDB vs. Microsoft Azure AI Search vs. SAP HANA

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Analytic DBMS for Hadoop

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Search-as-a-service for web and mobile app development

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

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Search engine

Relational DBMS

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

Vector 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	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

impala.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

couchdb.apache.org

azure.microsoft.com/en-us/services/search

www.sap.com/products/hana.html

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

learn.microsoft.com/en-us/azure/search

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Atos Convergence Creators

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Microsoft

SAP

Initial release

2013

2016

2005

2015

2010

Current release

4.1.0, June 2022

1703

3.3.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache version 2

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

Erlang

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Appliance or cloud-service

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

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

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

LDAP

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C#
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

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 or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: 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

LDAP bind authentication

Access rights for users can be defined per database

yes

using Azure authentication

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.