DBMS > Atos Standard Common Repository vs. GridGain vs. Oracle vs. RavenDB

System Properties Comparison Atos Standard Common Repository vs. GridGain vs. Oracle vs. RavenDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Widely used RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store
Key-value store

Key-value store
Relational DBMS

Relational DBMS

Document store

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

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.gridgain.com

www.oracle.com/database

ravendb.net

Technical documentation

www.gridgain.com/docs/index.html

docs.oracle.com/en/database

ravendb.net/docs

Developer

Atos Convergence Creators

GridGain Systems, Inc.

Oracle

Hibernating Rhinos

Initial release

2016

2007

1980

2010

Current release

1703

GridGain 8.5.1

23c, September 2023

5.4, July 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, C++, .Net

C and C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

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

Linux
macOS
Raspberry Pi
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

optional

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

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

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

LDAP

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

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

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

Server-side scripts

Stored procedures

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

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

isolation level can be parameterized

ACID, Cluster-wide transaction available

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'

User concepts

Access control

LDAP bind authentication

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.