DBMS > Google Cloud Datastore vs. GridGain vs. Oracle vs. SAP Advantage Database Server

System Properties Comparison Google Cloud Datastore vs. GridGain vs. Oracle vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used RDBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Document store

Key-value store
Relational DBMS

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.47
Rank	#76	Overall
	#12	Document stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

cloud.google.com/datastore

www.gridgain.com

www.oracle.com/database

www.sap.com/products/advantage-database-server.html

Technical documentation

cloud.google.com/datastore/docs

www.gridgain.com/docs/index.html

docs.oracle.com/en/database

Developer

Google

GridGain Systems, Inc.

Oracle

Sybase, SAP

Initial release

2008

2007

1980

1993

Current release

GridGain 8.5.1

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

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

Java, C++, .Net

C and C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

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

Linux
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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)

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

APIs and other access methods

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

Delphi
Perl
PHP

Server-side scripts

Stored procedures

using Google App Engine

yes (compute grid and cache interceptors can be used instead)

PL/SQL

also stored procedures in Java possible

yes

Triggers

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes (replicated cache)

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

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.

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

ACID

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'

caching of (temporary) tables can be configured

User concepts

Access control

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

Security Hooks for custom implementations

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.