DBMS > Apache Drill vs. Atos Standard Common Repository vs. BoltDB vs. Manticore Search vs. RocksDB

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. BoltDB vs. Manticore Search vs. RocksDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

An embedded key-value store for Go.

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

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

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Key-value store

Search engine

Key-value store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

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

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/boltdb/bolt

manticoresearch.com

rocksdb.org

Technical documentation

drill.apache.org/docs

manual.manticoresearch.com

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Atos Convergence Creators

Manticore Software

Facebook, Inc.

Initial release

2012

2016

2013

2017

2013

Current release

1.20.3, January 2023

1703

6.0, February 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

MIT License

Open Source

GPL version 2

Open Source

BSD

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

Server operating systems

Linux
OS X
Windows

Linux

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

optional

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

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

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

C++ API
Java API

Supported programming languages

C++

All languages with LDAP bindings

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Synchronous replication based on Galera library

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 or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

isolated transactions for atomic changes and binary logging for safe writes

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

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

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind 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.