DBMS > Google Cloud Datastore vs. Linter vs. Oracle vs. Percona Server for MongoDB vs. Sadas Engine

System Properties Comparison Google Cloud Datastore vs. Linter vs. Oracle vs. Percona Server for MongoDB vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

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

RDBMS for high security requirements

Widely used RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Secondary database models

Spatial DBMS

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	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

cloud.google.com/datastore

linter.ru

www.oracle.com/database

www.percona.com/mongodb/software/percona-server-for-mongodb

www.sadasengine.com

Technical documentation

cloud.google.com/datastore/docs

docs.oracle.com/en/database

docs.percona.com/percona-distribution-for-mongodb

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

Developer

Google

relex.ru

Oracle

Percona

SADAS s.r.l.

Initial release

2008

1990

1980

2015

2006

Current release

23c, September 2023

3.4.10-2.10, November 2017

8.0

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL Version 2

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 and C++

C++

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

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

Linux

AIX
Linux
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

proprietary protocol using JSON

JDBC
ODBC
Proprietary protocol

Supported programming languages

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

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

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax with the possibility to convert from PL/SQL

PL/SQL

also stored procedures in Java possible

JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

yes

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

Eventual Consistency
Immediate 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

ACID

isolation level can be parameterized

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

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

yes

via In-Memory Engine

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)

fine grained access rights according to SQL-standard

Access rights for users and roles

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.