DBMS > Heroic vs. LokiJS vs. OrigoDB vs. Percona Server for MongoDB vs. PostGIS

System Properties Comparison Heroic vs. LokiJS vs. OrigoDB vs. Percona Server for MongoDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

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

In-memory JavaScript DBMS

A fully ACID in-memory object graph database

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

Spatial extension of PostgreSQL

Primary database model

Time Series DBMS

Document store

Document store
Object oriented DBMS

Document store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/spotify/heroic

github.com/techfort/LokiJS

origodb.com

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

postgis.net

Technical documentation

spotify.github.io/heroic

techfort.github.io/LokiJS

origodb.com/docs

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

postgis.net/documentation

Developer

Spotify

Robert Friberg et al

Percona

Initial release

2014

2009

under the name LiveDB

2015

2005

Current release

3.4.10-2.10, November 2017

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL Version 2

Open Source

GPL v2.0

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

JavaScript

C++

Server operating systems

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

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

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.

can be achieved using .NET

yes

Secondary indexes

yes

via Elasticsearch

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

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

JavaScript API

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

Supported programming languages

JavaScript

.Net

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

View functions in JavaScript

yes

JavaScript

user defined functions

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

atomic operations within a single collection possible

ACID

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

Write ahead log

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

Role based authorization

Access rights for users and roles

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

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

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

The essential guide to MongoDB security
2 February 2017, InfoWorld

The Case Against the Server Side Public License (SSPL)
11 October 2022, The New Stack

provided by Google News

Share this page