DBMS > Apache Impala vs. DataFS vs. Microsoft Azure Cosmos DB vs. SAP Adaptive Server

System Properties Comparison Apache Impala vs. DataFS vs. Microsoft Azure Cosmos DB vs. SAP Adaptive Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Relational DBMS

Object oriented DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

Graph DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

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

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

impala.apache.org

newdatabase.com

azure.microsoft.com/services/cosmos-db

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

Technical documentation

impala.apache.org/impala-docs.html

dev.mobiland.com/Overview.xsp

learn.microsoft.com/azure/cosmos-db

help.sap.com/docs/SAP_ASE

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Mobiland AG

Microsoft

SAP, Sybase

Initial release

2013

2018

2014

1987

Current release

4.1.0, June 2022

1.1.263, October 2022

16.0

License

Commercial or Open Source

Open Source

Apache Version 2

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++

C and C++

Server operating systems

Linux

Windows

hosted

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

yes

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
Proprietary client DLL
WinRT client

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

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

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
VB.Net

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

JavaScript

Java and Transact-SQL

Triggers

no, except callback-events from server when changes happened

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Proprietary Sharding system

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

ACID

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 for users, groups and roles

based on Apache Sentry and Kerberos

Windows-Profile

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.