DBMS > Apache Impala vs. Ehcache vs. EJDB vs. MySQL vs. Qdrant

System Properties Comparison Apache Impala vs. Ehcache vs. EJDB vs. MySQL vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A widely adopted Java cache with tiered storage options

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

A high-performance vector database with neural network or semantic-based matching

Primary database model

Key/Value like access via memcached API

Vector DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

impala.apache.org

www.ehcache.org

github.com/Softmotions/ejdb

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

impala.apache.org/impala-docs.html

www.ehcache.org/documentation

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

qdrant.tech/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Terracotta Inc, owned by Software AG

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Initial release

2013

2009

2012

1995

2021

Current release

4.1.0, June 2022

3.10.0, March 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Rust

Server operating systems

Linux

All OS with a Java VM

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JCache

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

by using Terracotta Server

none

Multi-source replication
Source-replica replication

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Users with fine-grained authorization concept

no user groups or roles

Key-based authentication

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.