DBMS > Google Cloud Datastore vs. MarkLogic vs. RocksDB vs. Sadas Engine

System Properties Comparison Google Cloud Datastore vs. MarkLogic vs. RocksDB vs. Sadas Engine

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

Operational and transactional Enterprise NoSQL database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Relational DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

cloud.google.com/datastore

www.marklogic.com

rocksdb.org

www.sadasengine.com

Technical documentation

cloud.google.com/datastore/docs

docs.marklogic.com

github.com/facebook/rocksdb/wiki

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Google

MarkLogic Corp.

Facebook, Inc.

SADAS s.r.l.

Initial release

2008

2001

2013

2006

Current release

11.0, December 2022

8.11.4, April 2024

8.0

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD

commercial

free trial version 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++

Server operating systems

hosted

Linux
OS X
Windows

Linux

AIX
Linux
Windows

Data scheme

schema-free

Schema can be enforced

schema-free

yes

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

APIs and other access methods

gRPC (using protocol buffers) 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

C++ API
Java API

JDBC
ODBC
Proprietary protocol

Supported programming languages

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

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

via XQuery or JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

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

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.

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

ACID

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

yes

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

yes

managed by 'Learn by Usage'

User concepts

Access control

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

Role-based access control at the document and subdocument levels

Access rights for users, groups and roles 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.