DBMS > EsgynDB vs. Greenplum vs. LevelDB vs. Microsoft Azure Cosmos DB vs. RavenDB

System Properties Comparison EsgynDB vs. Greenplum vs. LevelDB vs. Microsoft Azure Cosmos DB vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

www.esgyn.cn

greenplum.org

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

ravendb.net

Technical documentation

docs.greenplum.org

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

Developer

Esgyn

Pivotal Software Inc.

Google

Microsoft

Hibernating Rhinos

Initial release

2015

2005

2011

2014

2010

Current release

7.0.0, September 2023

1.23, February 2021

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

commercial

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

C++

Server operating systems

Linux

Illumos
Linux
OS X
Windows

hosted

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

since Version 4.2

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
Java
Perl
Python
R

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

none

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.