DBMS > Ignite vs. Oracle vs. Sqrrl vs. Tarantool

System Properties Comparison Ignite vs. Oracle vs. Sqrrl vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Widely used RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

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

Document store
Graph DBMS
Key-value store
Wide column store

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

ignite.apache.org

www.oracle.com/database

sqrrl.com

www.tarantool.io

Technical documentation

apacheignite.readme.io/docs

docs.oracle.com/en/database

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Oracle

Amazon

originally Sqrrl Data, Inc.

Initial release

2015

1980

2012

2008

Current release

Apache Ignite 2.6

23c, September 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache 2.0

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

C++, Java, .Net

C and C++

Java

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

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

Linux

BSD
Linux
macOS

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

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)

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

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

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

Sharding

making use of Hadoop

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

selectable replication factor

making use of Hadoop

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

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, 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, 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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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

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.