DBMS > LokiJS vs. Oracle Berkeley DB vs. Realm vs. Snowflake

System Properties Comparison LokiJS vs. Oracle Berkeley DB vs. Realm vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory JavaScript DBMS

Widely used in-process key-value store

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Relational DBMS

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

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/techfort/LokiJS

www.oracle.com/database/technologies/related/berkeleydb.html

realm.io

www.snowflake.com

Technical documentation

techfort.github.io/LokiJS

docs.oracle.com/cd/E17076_05/html/index.html

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2014

1994

2014

Current release

18.1.40, May 2020

License

Commercial or Open Source

Open Source

commercial license available

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

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

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

only for the SQL API

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

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

In-memory capabilities

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

yes

In-Memory realm

User concepts

Access control

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.