DBMS > EJDB vs. Geode vs. NSDb vs. Postgres-XL vs. Yanza

System Properties Comparison EJDB vs. Geode vs. NSDb vs. Postgres-XL vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

github.com/Softmotions/ejdb

geode.apache.org

nsdb.io

www.postgres-xl.org

yanza.com

Technical documentation

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

geode.apache.org/docs

nsdb.io/Architecture

www.postgres-xl.org/documentation

Developer

Softmotions

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

Yanza

Initial release

2012

2002

2017

2014

since 2012, originally named StormDB

2015

Current release

1.1, February 2017

10 R1, October 2018

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2.0

Open Source

Mozilla public license

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, Scala

Server operating systems

server-less

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

Windows

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

yes: int, bigint, decimal, string

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

XML type, but no XML query functionality

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

in-process shared library

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
WebSocket

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

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

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

Java
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, on a single node

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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 per client and object definable

fine grained access rights according to SQL-standard

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

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

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

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

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

Share this page