DBMS > Ignite vs. InterSystems Caché vs. Riak TS vs. SQLite

System Properties Comparison Ignite vs. InterSystems Caché vs. Riak TS vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is 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.

A multi-model DBMS and application server

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

ignite.apache.org

www.intersystems.com/products/cache

www.sqlite.org

Technical documentation

apacheignite.readme.io/docs

docs.intersystems.com

www.tiot.jp/riak-docs/riak/ts/latest

www.sqlite.org/docs.html

Developer

Apache Software Foundation

InterSystems

Open Source, formerly Basho Technologies

Dwayne Richard Hipp

Initial release

2015

1997

2015

2000

Current release

Apache Ignite 2.6

2018.1.4, May 2020

3.0.0, September 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

Erlang

Server operating systems

Linux
OS X
Solaris
Windows

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X

server-less

Data scheme

yes

depending on used data model

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

restricted

yes

SQL

Support of SQL

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

yes

yes, limited

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

.NET Client API
JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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)

yes

Erlang

Triggers

yes (cache interceptors and events)

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

Security Hooks for custom implementations

Access rights for users, groups 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.