DBMS > Adabas vs. IBM Cloudant vs. InterSystems Caché vs. Snowflake

System Properties Comparison Adabas vs. IBM Cloudant vs. InterSystems Caché vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

used typically together with the Natural programming platform

Database as a Service offering based on Apache CouchDB

A multi-model DBMS and application server

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Multivalue DBMS

Document store

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

Document store

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.ibm.com/products/cloudant

www.intersystems.com/products/cache

www.snowflake.com

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.intersystems.com

docs.snowflake.net/manuals/index.html

Developer

Software AG

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

InterSystems

Snowflake Computing Inc.

Initial release

1971

2010

1997

2014

Current release

2018.1.4, May 2020

License

Commercial or Open Source

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

depending on used data model

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Natural

C#
Java
JavaScript
Objective-C
PHP
Ruby

C#
C++
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

View functions (Map-Reduce) in JavaScript

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

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.

yes

User concepts

Access control

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

Access rights for users can be defined per database

Access rights for users, groups and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.