DBMS > IBM Cloudant vs. Oracle vs. PostGIS vs. SAP SQL Anywhere

System Properties Comparison IBM Cloudant vs. Oracle vs. PostGIS vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

Spatial extension of PostgreSQL

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Relational DBMS

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

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Website

www.ibm.com/products/cloudant

www.oracle.com/database

postgis.net

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

postgis.net/documentation

help.sap.com/docs/SAP_SQL_Anywhere

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

SAP

formerly Sybase

Initial release

2010

1980

2005

1992

Current release

23c, September 2023

3.4.2, February 2024

17, July 2015

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL v2.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

Erlang

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

user defined functions

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

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

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.