DBMS > BoltDB vs. Microsoft Access vs. Percona Server for MongoDB vs. RocksDB vs. Solr

System Properties Comparison BoltDB vs. Microsoft Access vs. Percona Server for MongoDB vs. RocksDB vs. Solr

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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.)

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

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

github.com/boltdb/bolt

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

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

rocksdb.org

solr.apache.org

Technical documentation

developer.microsoft.com/en-us/access

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

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Microsoft

Percona

Facebook, Inc.

Apache Software Foundation

Initial release

2013

1992

2015

2013

2006

Current release

1902 (16.0.11328.20222), March 2019

3.4.10-2.10, November 2017

9.2.1, May 2024

9.6.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Bundled with Microsoft Office

Open Source

GPL Version 2

Open Source

BSD

Open Source

Apache Version 2

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

Solr Parallel SQL Interface

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol using JSON

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

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

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Java plugins

Triggers

yes

since Access 2010 using the ACE-engine

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

but no files for transaction logging

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

via In-Memory Engine

yes

User concepts

Access control

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

Access rights for users and roles

yes

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.