DBMS > IBM Cloudant vs. SAP HANA

System Properties Comparison IBM Cloudant vs. SAP HANA

Please select another system to include it in the comparison.

Our visitors often compare IBM Cloudant and SAP HANA with MongoDB, Microsoft Azure Cosmos DB and Amazon DynamoDB.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.29
Rank	#93	Overall
	#17	Document stores

Score	50.36
Rank	#23	Overall
	#16	Relational DBMS

Website

www.ibm.com/cloud/cloudant

www.sap.com/products/hana.html

Technical documentation

cloud.ibm.com/docs/Cloudant

help.sap.com/hana

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP

Initial release

2010

Current release

2.0 SPS06 (March 4, 2022), March 2022

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Server operating systems

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source 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

Eventual Consistency

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

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

Access rights for users can be defined per database

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.