DBMS > Heroic vs. Ignite vs. LokiJS vs. Percona Server for MongoDB

System Properties Comparison Heroic vs. Ignite vs. LokiJS vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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 JavaScript DBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Document store

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

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	3.64
Rank	#89	Overall
	#13	Key-value stores
	#48	Relational DBMS

Score	0.48
Rank	#262	Overall
	#42	Document stores

Score	0.55
Rank	#253	Overall
	#39	Document stores

Website

github.com/spotify/heroic

ignite.apache.org

github.com/techfort/LokiJS

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

spotify.github.io/heroic

apacheignite.readme.io/docs

techfort.github.io/LokiJS

docs.percona.com/percona-distribution-for-mongodb

Developer

Spotify

Apache Software Foundation

Percona

Initial release

2014

2015

2014

2015

Current release

Apache Ignite 2.6

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL Version 2

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

JavaScript

C++

Server operating systems

Linux
OS X
Solaris
Windows

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

Linux

Data scheme

schema-free

yes

schema-free

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

via Elasticsearch

yes

via views

yes

SQL

Support of SQL

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

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

JavaScript API

proprietary protocol using JSON

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

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

View functions in JavaScript

JavaScript

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

In-memory capabilities

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

yes

via In-Memory Engine

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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: An Overview
6 September 2023, Open Source For You

ArcGIS and Apache Log4j Vulnerabilities
22 May 2023, Esri

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

provided by Google News

LokiJS - A JavaScript Database
18 November 2014, iProgrammer

provided by Google News

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

How to Plan Your MongoDB Upgrade
29 January 2024, The New Stack

Is database-as-a-service in Percona's future?
23 May 2022, VentureBeat

provided by Google News

Share this page