DBMS > Ignite vs. OrigoDB vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison Ignite vs. OrigoDB vs. SAP SQL Anywhere vs. Splunk

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.

A fully ACID in-memory object graph database

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Search engine

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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

ignite.apache.org

origodb.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

apacheignite.readme.io/docs

origodb.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Robert Friberg et al

SAP

formerly Sybase

Splunk Inc.

Initial release

2015

2009

under the name LiveDB

1992

2003

Current release

Apache Ignite 2.6

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

Limited free edition and free developer edition available

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

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

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

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

Splunk Search Processing Language for search commands

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes (cache interceptors and events)

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

Database mirroring

Multi-source replication

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

depending on model

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

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

Related products and services

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

More resources

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the 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

SAP vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

SAP Again Named a Leader in 2021 Gartner® Magic Quadrant™ for Cloud Database Management Systems
16 December 2021, SAP News

SAP launches HANA cloud platform, partners with Siemens, Intel
6 May 2015, Channel Daily News

AWS, IBM, Microsoft, Google emerge Cloud DBMS leaders
22 December 2022, Daily Host News

provided by Google News

Share this page