DBMS > Hazelcast vs. JanusGraph vs. Percona Server for MongoDB vs. SQLite vs. Tarantool

System Properties Comparison Hazelcast vs. JanusGraph vs. Percona Server for MongoDB vs. SQLite vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Widely used embeddable, in-process RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

with Tarantool/GIS extension

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

hazelcast.com

janusgraph.org

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

www.sqlite.org

www.tarantool.io

Technical documentation

hazelcast.org/imdg/docs

docs.janusgraph.org

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

www.sqlite.org/docs.html

www.tarantool.io/en/doc

Developer

Hazelcast

Linux Foundation; originally developed as Titan by Aurelius

Percona

Dwayne Richard Hipp

Initial release

2008

2017

2015

2000

2008

Current release

5.3.6, November 2023

0.6.3, February 2023

3.4.10-2.10, November 2017

3.46.0 (23 May 2024), May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

GPL Version 2

Open Source

Public Domain

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Server operating systems

All OS with a Java VM

Linux
OS X
Unix
Windows

Linux

server-less

BSD
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

string, double, decimal, uuid, integer, blob, boolean, datetime

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

Full-featured ANSI SQL support

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Open binary protocol

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Clojure
Java
Python

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

JavaScript

Lua, C and SQL stored procedures

Triggers

yes

Events

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Source-replica replication

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

yes, write ahead logging

In-memory capabilities

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

yes

via In-Memory Engine

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Role-based access control

User authentification and security via Rexster Graph Server

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.