DBMS > BoltDB vs. JanusGraph vs. Manticore Search vs. RocksDB vs. Tarantool

System Properties Comparison BoltDB vs. JanusGraph vs. Manticore Search vs. RocksDB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A Graph DBMS optimized for distributed clusters

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

Multi-storage database for search, including full-text search.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

docs.janusgraph.org

manual.manticoresearch.com

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

Linux Foundation; originally developed as Titan by Aurelius

Manticore Software

Facebook, Inc.

Initial release

2013

2017

2013

2008

Current release

0.6.3, February 2023

6.0, February 2023

8.11.4, April 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

GPL version 2

Open Source

BSD

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

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
macOS
Windows

Linux

BSD
Linux
macOS

Data scheme

schema-free

yes

Fixed schema

schema-free

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

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

C++ API
Java API

Open binary protocol

Supported programming languages

Clojure
Java
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

yes

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning

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

none

yes

Synchronous replication based on Galera library

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

yes

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

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes

The original contents of fields are not stored in the Manticore index.

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

User authentification and security via Rexster Graph Server

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.