DBMS > Ignite vs. SAP HANA vs. Sequoiadb vs. Solr

System Properties Comparison Ignite vs. SAP HANA vs. Sequoiadb vs. Solr

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.

In-memory, column based data store. Available as appliance or cloud service

NewSQL database with distributed OLTP and SQL

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Document store
Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

ignite.apache.org

www.sap.com/products/hana.html

www.sequoiadb.com

solr.apache.org

Technical documentation

apacheignite.readme.io/docs

help.sap.com/hana

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

solr.apache.org/resources.html

Developer

Apache Software Foundation

SAP

Sequoiadb Ltd.

Apache Software Foundation

Initial release

2015

2010

2013

2006

Current release

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

also available as a cloud based 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++

Java

Server operating systems

Linux
OS X
Solaris
Windows

Appliance or cloud-service

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

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

yes

SQL-like query language

Solr Parallel SQL Interface

APIs and other access methods

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

JDBC
ODBC

proprietary protocol using JSON

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C++
Java
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

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

SQLScript, R

JavaScript

Java plugins

Triggers

yes (cache interceptors and events)

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

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

yes

simple password-based access control

yes

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.