DBMS > Adabas vs. Ignite vs. Microsoft Azure Cosmos DB vs. WakandaDB

System Properties Comparison Adabas vs. Ignite vs. Microsoft Azure Cosmos DB vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Globally distributed, horizontally scalable, multi-model database service

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Multivalue DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

ignite.apache.org

azure.microsoft.com/services/cosmos-db

wakanda.github.io

Technical documentation

apacheignite.readme.io/docs

learn.microsoft.com/azure/cosmos-db

wakanda.github.io/doc

Developer

Software AG

Apache Software Foundation

Microsoft

Wakanda SAS

Initial release

1971

2015

2014

2012

Current release

Apache Ignite 2.6

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

AGPLv3, extended commercial license 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, .Net

C++, JavaScript

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Solaris
Windows

hosted

Linux
OS X
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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

RESTful HTTP API

Supported programming languages

Natural

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript

Server-side scripts

Stored procedures

in Natural

yes (compute grid and cache interceptors can be used instead)

JavaScript

yes

Triggers

yes (cache interceptors and events)

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes (replicated cache)

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

Immediate Consistency

Foreign keys

Referential integrity

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.

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

Security Hooks for custom implementations

Access rights can be defined down to the item level

yes

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.