DBMS > BoltDB vs. Ignite vs. LeanXcale vs. Lovefield vs. Splunk

System Properties Comparison BoltDB vs. Ignite vs. LeanXcale vs. Lovefield vs. Splunk

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 highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Embeddable relational database for web apps written in pure JavaScript

Analytics Platform for Big Data

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Search engine

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

github.com/boltdb/bolt

ignite.apache.org

www.leanxcale.com

google.github.io/lovefield

www.splunk.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

LeanXcale

Google

Splunk Inc.

Initial release

2013

2015

2014

2003

Current release

Apache Ignite 2.6

2.1.12, February 2017

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

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

C++, Java, .Net

JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

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

Data scheme

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

yes

through Apache Derby

SQL-like query language

via JavaScript builder pattern

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

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

HTTP REST

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
Java
Scala

JavaScript

C#
Java
JavaScript
PHP
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

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

none

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

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

User concepts

Access control

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

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.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

Combining operational and analytical databases in a single platform
26 May 2017, Cordis News

provided by Google News

Share this page