DBMS > EsgynDB vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Splunk

System Properties Comparison EsgynDB vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Splunk

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Globally distributed, horizontally scalable, multi-model database service

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Secondary database models

Spatial DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

www.esgyn.cn

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

www.splunk.com

Technical documentation

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

docs.splunk.com/Documentation/Splunk

Developer

Esgyn

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

Splunk Inc.

Initial release

2015

1984

2014

2003

Current release

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Limited free edition and free developer edition 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

AIX
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

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

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
Java
Perl
PHP
Python

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

C#
Java
JavaScript
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

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

Eventual 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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.