DBMS > Ignite vs. Lovefield vs. Splunk vs. Tkrzw vs. Yaacomo

System Properties Comparison Ignite vs. Lovefield vs. Splunk vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and 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.

Embeddable relational database for web apps written in pure JavaScript

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store
Relational DBMS

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.29
Rank	#293	Overall
	#133	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

ignite.apache.org

google.github.io/lovefield

www.splunk.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

apacheignite.readme.io/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Google

Splunk Inc.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2015

2014

2003

2020

2009

Current release

Apache Ignite 2.6

2.1.12, February 2017

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0

commercial

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

JavaScript

C++

Server operating systems

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Solaris
Windows

Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

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

SQL-like query language

via JavaScript builder pattern

Splunk Search Processing Language for search commands

yes

APIs and other access methods

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

HTTP REST

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

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

yes

Triggers

yes (cache interceptors and events)

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Multi-source replication

none

Source-replica 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

Immediate Consistency

Foreign keys

Referential integrity

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

using specific database classes

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles

fine grained access rights according to SQL-standard

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

Share this page