DBMS > Hawkular Metrics vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. SAP Adaptive Server

System Properties Comparison Hawkular Metrics vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. SAP Adaptive Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Globally distributed, horizontally scalable, multi-model database service

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

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

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	37.12
Rank	#25	Overall
	#17	Relational DBMS

Website

www.hawkular.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/products/azure-sql/database

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

Technical documentation

www.hawkular.org/hawkular-metrics/docs/user-guide

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/docs/SAP_ASE

Developer

Community supported by Red Hat

Microsoft

SAP, Sybase

Initial release

2014

2010

1987

Current release

V12

16.0

License

Commercial or Open Source

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

Java

C++

C and C++

Server operating systems

Linux
OS X
Windows

hosted

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

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

SQL-like query language

yes

APIs and other access methods

HTTP REST

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

ADO.NET
JDBC
ODBC

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

Supported programming languages

Go
Java
Python
Ruby

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

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

JavaScript

Transact SQL

Java and Transact-SQL

Triggers

yes

via Hawkular Alerting

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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.

User concepts

Access control

Access rights can be defined down to the item level

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.