DBMS > GridGain vs. Oracle vs. Raima Database Manager vs. Tarantool

System Properties Comparison GridGain vs. Oracle vs. Raima Database Manager vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used RDBMS

RDBMS with a small footprint, either embedded into an application or used as a database server

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Key-value store
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

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	0.48
Rank	#261	Overall
	#122	Relational DBMS
	#22	Time Series DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

www.gridgain.com

www.oracle.com/database

raima.com

www.tarantool.io

Technical documentation

www.gridgain.com/docs/index.html

docs.oracle.com/en/database

docs.raima.com

www.tarantool.io/en/doc

Developer

GridGain Systems, Inc.

Oracle

Raima Inc.

Initial release

2007

1980

1984

2008

Current release

GridGain 8.5.1

23c, September 2023

15, June 2021

2.10.0, May 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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, C++, .Net

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

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

Android
HP-UX
Integrity RTOS
iOS
Linux
OS X
QNX
Solaris
VxWorks
Windows

BSD
Linux
macOS

Data scheme

yes

Schemaless in JSON and XML columns

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Exporting/Importing of XML structures possible

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
RESTful HTTP API

Open binary protocol

Supported programming languages

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
C++
Objective-C
PL/SQL

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

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

PL/SQL

also stored procedures in Java possible

yes

based on the ANSI/ISO SQL Persistent Stored Modules (PSM) specification

Lua, C and SQL stored procedures

Triggers

yes (cache interceptors and events)

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication
Source-replica replication

Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

Raima Database Manager (RDM) is an embedded time-series database optimized to run...
» more

Competitive advantages

Decreased time-to-market Industry-standard interfaces & tools for making your job...
» more

Typical application scenarios

Typical use cases include: Internet of Things (IoT) Embedded In-Memory Database Time-Series...
» more

Key customers

Infor, ABB, The Boeing Company, BAE Systems, Dow Jones, Dun & Bradstreet, Fujitsu,...
» more

Market metrics

Over 30 000 applications developers worldwide have field-tested RDM products More...
» more

Licensing and pricing models

Just as the technical aspects of Raima Database Manager are flexible, so are the...
» more

News

Raima Unveils RaimaDB 16.0: Elevating Database Performance and User Experience
29 February 2024

Raima Announces Release of Raima Database Manager (RDM) v15, a Powerful Embedded Time Series Database
10 June 2021

Raima Announces Release of Raima Database Manager (RDM) v14.2, a Powerful IoT Edge Embedded Database
8 October 2020

Raima Joins BlackBerry QNX Channel Partner Program to Deliver Safety-Critical and Secure Software Solutions
1 October 2020

Raima Expands Their Reseller Network in Asia
19 May 2020

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.