DBMS > Ehcache vs. Ignite vs. OrigoDB vs. Sequoiadb

System Properties Comparison Ehcache vs. Ignite vs. OrigoDB vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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 fully ACID in-memory object graph database

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Document store
Relational DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

Technical documentation

www.ehcache.org/documentation

apacheignite.readme.io/docs

origodb.com/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Terracotta Inc, owned by Software AG

Apache Software Foundation

Robert Friberg et al

Sequoiadb Ltd.

Initial release

2009

2015

2009

under the name LiveDB

2013

Current release

3.10.0, March 2022

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

oid, date, timestamp, binary, regex

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language

APIs and other access methods

JCache

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

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

Supported programming languages

Java

C#
C++
Java
PHP
Python
Ruby
Scala

.Net

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

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

yes

JavaScript

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes (replicated cache)

Source-replica replication

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

Write ahead log

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

Role based authorization

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page