DBMS > EJDB vs. EsgynDB vs. Geode vs. Percona Server for MongoDB

System Properties Comparison EJDB vs. EsgynDB vs. Geode vs. Percona Server for MongoDB

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)

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

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

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.55
Rank	#253	Overall
	#39	Document stores

Website

github.com/Softmotions/ejdb

www.esgyn.cn

geode.apache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

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

geode.apache.org/docs

docs.percona.com/percona-distribution-for-mongodb

Developer

Softmotions

Esgyn

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Percona

Initial release

2012

2015

2002

2015

Current release

1.1, February 2017

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

C++, Java

Java

C++

Server operating systems

server-less

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
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

ACID

yes, on a single node

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.

yes

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

Access rights for users and 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

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

How to Plan Your MongoDB Upgrade
29 January 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

Is database-as-a-service in Percona's future?
23 May 2022, VentureBeat

Percona Joins the Google Cloud Platform Partner Program as a Service Partner
5 April 2016, Yahoo Movies UK

provided by Google News

Share this page