DBMS > EsgynDB vs. Geode vs. Microsoft Azure Cosmos DB vs. SAP HANA vs. Yanza

System Properties Comparison EsgynDB vs. Geode vs. Microsoft Azure Cosmos DB vs. SAP HANA vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

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

Globally distributed, horizontally scalable, multi-model database service

In-memory, column based data store. Available as appliance or cloud service

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.esgyn.cn

geode.apache.org

azure.microsoft.com/services/cosmos-db

www.sap.com/products/hana.html

yanza.com

Technical documentation

geode.apache.org/docs

learn.microsoft.com/azure/cosmos-db

help.sap.com/hana

Developer

Esgyn

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

Microsoft

SAP

Yanza

Initial release

2015

2002

2014

2010

2015

Current release

1.1, February 2017

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based 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

C++, Java

Java

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Appliance or cloud-service

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

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

JDBC
ODBC

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

JavaScript

SQLScript, R

Triggers

yes

Cache Event Listeners

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication

yes

Implicit feature of the cloud service

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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

fine grained access rights according to SQL-standard

Access rights per client and object definable

Access rights can be defined down to the item level

yes

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.