DBMS > EsgynDB vs. Ingres vs. Microsoft Azure Cosmos DB vs. Oracle Coherence

System Properties Comparison EsgynDB vs. Ingres vs. Microsoft Azure Cosmos DB vs. Oracle Coherence

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Well established RDBMS

Globally distributed, horizontally scalable, multi-model database service

Oracles in-memory data grid solution

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

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

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

www.esgyn.cn

www.actian.com/databases/ingres

azure.microsoft.com/services/cosmos-db

www.oracle.com/java/coherence

Technical documentation

docs.actian.com/ingres

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/en/middleware/standalone/coherence

Developer

Esgyn

Actian Corporation

Microsoft

Oracle

Initial release

2015

1974

originally developed at University Berkely in early 1970s

2014

2007

Current release

11.2, May 2022

14.1, August 2023

License

Commercial or Open Source

commercial

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

Java

Server operating systems

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

All OS with a Java VM

Data scheme

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

JCache
JPA
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

.Net
C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

JavaScript

Triggers

yes

JavaScript

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Ingres Replicator

yes

Implicit feature of the cloud service

yes, with selectable consistency level

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

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

configurable

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes

optionally

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 can be defined down to the item level

authentification to access the cache via certificates or http basic authentication

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.