DBMS > EJDB vs. GeoMesa vs. Hazelcast vs. Percona Server for MySQL

System Properties Comparison EJDB vs. GeoMesa vs. Hazelcast vs. Percona Server for MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A widely adopted in-memory data grid

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

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

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

hazelcast.com

www.percona.com/software/mysql-database/percona-server

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

hazelcast.org/imdg/docs

www.percona.com/downloads/Percona-Server-LATEST

Developer

Softmotions

CCRi and others

Hazelcast

Percona

Initial release

2012

2014

2008

Current release

5.0.0, May 2024

5.3.6, November 2023

8.0.36-28, 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2

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

Scala

Java

C and C++

Server operating systems

server-less

All OS with a Java VM

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

in-process shared library

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

Replicated Map

Multi-source replication
Source-replica replication
XtraDB Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

provided by Google News

Fusion-io Flash-Aware Compression Boosts Capacity for MySQL
31 May 2024, Data Center Knowledge

Update or migrate? Planning for MySQL 5.7 EOL
22 June 2023, InfoWorld

Sizing Up Servers: Intel's Skylake-SP Xeon versus AMD's EPYC 7000 - The Server CPU Battle of the Decade?
11 July 2017, AnandTech

ScaleFlux computational storage makes Percona MySQL faster – Blocks and Files
5 August 2020, Blocks and Files

How to deploy the Percona database performance monitor with Docker
24 February 2023, TechRepublic

provided by Google News

Share this page