DBMS > Apache Impala vs. Coveo vs. Hazelcast vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Impala vs. Coveo vs. Hazelcast vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

A widely adopted in-memory data grid

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Search engine

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

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.11
Rank	#118	Overall
	#11	Search engines

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

impala.apache.org

www.coveo.com

hazelcast.com

azure.microsoft.com/services/cosmos-db

Technical documentation

impala.apache.org/impala-docs.html

docs.coveo.com

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Coveo

Hazelcast

Microsoft

Initial release

2013

2012

2008

2014

Current release

4.1.0, June 2022

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; commercial licenses 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

Server operating systems

Linux

hosted

All OS with a Java VM

hosted

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

the object must implement a serialization strategy

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Event Listeners, Executor Services

JavaScript

Triggers

yes

Events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Replicated Map

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

one or two-phase-commit; repeatable reads; read commited

Multi-item ACID transactions with snapshot isolation within a partition

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

granular access controls, API key management, content filters

Role-based access control

Access rights can be defined down to the item level

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.