DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. Prometheus vs. SAP Adaptive Server

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. Prometheus vs. SAP Adaptive Server

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Application development environment with integrated database management system

Open-source Time Series DBMS and monitoring system

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.progress.com/openedge

prometheus.io

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

documentation.progress.com/output/ua/OpenEdge_latest

prometheus.io/docs

help.sap.com/docs/SAP_ASE

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Progress Software Corporation

SAP, Sybase

Initial release

2010

2014

1984

2015

1987

Current release

OpenEdge 12.2, March 2020

16.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Erlang

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

close to SQL 92

yes

APIs and other access methods

RESTful HTTP/JSON API

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

JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Progress proprietary ABL (Advanced Business Language)

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Java and Transact-SQL

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

since Version 11.4

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication

yes

by Federation

Multi-source replication
Source-replica replication

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

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

Access rights can be defined down to the item level

Users and groups

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.