DBMS > Ignite vs. Oracle Coherence vs. RisingWave vs. SQLite

System Properties Comparison Ignite vs. Oracle Coherence vs. RisingWave vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Oracles in-memory data grid solution

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	0.58
Rank	#242	Overall
	#111	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

ignite.apache.org

www.oracle.com/java/coherence

www.risingwave.com/database

www.sqlite.org

Technical documentation

apacheignite.readme.io/docs

docs.oracle.com/en/middleware/standalone/coherence

docs.risingwave.com/docs/current/intro

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Oracle

RisingWave Labs

Dwayne Richard Hipp

Initial release

2015

2007

2022

2000

Current release

Apache Ignite 2.6

14.1, August 2023

1.2, September 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Java

Rust

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

Docker
Linux
macOS

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

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

JCache
JPA
RESTful HTTP API

JDBC
PostgreSQL wire protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C++
Java

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

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

UDFs in Python or Java

Triggers

yes (cache interceptors and events)

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, with selectable consistency level

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

optionally

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Security Hooks for custom implementations

authentification to access the cache via certificates or http basic authentication

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.