DBMS > BoltDB vs. Manticore Search vs. Microsoft Access vs. RocksDB vs. Vitess

System Properties Comparison BoltDB vs. Manticore Search vs. Microsoft Access vs. RocksDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/boltdb/bolt

manticoresearch.com

www.microsoft.com/en-us/microsoft-365/access

rocksdb.org

vitess.io

Technical documentation

manual.manticoresearch.com

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Manticore Software

Microsoft

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2017

1992

2013

Current release

6.0, February 2023

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Docker
Linux
macOS

Data scheme

schema-free

Fixed schema

yes

schema-free

yes

Typing

predefined data types such as float or date

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

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 index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

but no files for transaction logging

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

yes

but no files for transaction logging

yes

In-memory capabilities

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

yes

User concepts

Access control

a simple user-level security was built in till version Access 2003

Users with fine-grained authorization concept

no user groups or 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.