DBMS > Atos Standard Common Repository vs. H2 vs. Ignite vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. H2 vs. Ignite vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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.

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.h2database.com

ignite.apache.org

www.splunk.com

Technical documentation

www.h2database.com/html/main.html

apacheignite.readme.io/docs

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

Thomas Mueller

Apache Software Foundation

Splunk Inc.

Initial release

2016

2005

2015

2003

Current release

1703

2.2.220, July 2023

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

Apache 2.0

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

Java

C++, Java, .Net

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

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

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

JDBC
ODBC

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

HTTP REST

Supported programming languages

All languages with LDAP bindings

Java

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

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

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

With clustering: 2 database servers on different computers operate on identical copies of a database

yes (replicated cache)

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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

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

yes, multi-version concurrency control (MVCC)

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

LDAP bind authentication

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

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 Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

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