DBMS > Google Cloud Datastore vs. IBM Cloudant vs. MarkLogic vs. Oracle

System Properties Comparison Google Cloud Datastore vs. IBM Cloudant vs. MarkLogic vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Database as a Service offering based on Apache CouchDB

Operational and transactional Enterprise NoSQL database

Widely used RDBMS

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

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

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

cloud.google.com/datastore

www.ibm.com/products/cloudant

www.marklogic.com

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

docs.marklogic.com

docs.oracle.com/en/database

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

MarkLogic Corp.

Oracle

Initial release

2008

2010

2001

1980

Current release

11.0, December 2022

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

restricted free version is 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

Erlang

C++

C and C++

Server operating systems

hosted

Linux
OS X
Windows

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

Data scheme

schema-free

Schema can be enforced

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes, details here

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

SQL-like query language (GQL)

yes

SQL92

yes

with proprietary extensions

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
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

Server-side scripts

Stored procedures

using Google App Engine

View functions (Map-Reduce) in JavaScript

yes

via XQuery or JavaScript

PL/SQL

also stored procedures in Java possible

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a document possible

ACID

can act as a resource manager in an XA/JTA transaction

ACID

isolation level can be parameterized

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, with Range Indexes

yes

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users can be defined per database

Role-based access control at the document and subdocument levels

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.