DBMS > Manticore Search vs. Microsoft Access vs. RocksDB vs. Solr

System Properties Comparison Manticore Search vs. Microsoft Access vs. RocksDB vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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)

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

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

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

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

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

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

manticoresearch.com

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

rocksdb.org

solr.apache.org

Technical documentation

manual.manticoresearch.com

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Manticore Software

Microsoft

Facebook, Inc.

Apache Software Foundation

Initial release

2017

1992

2013

2006

Current release

6.0, February 2023

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

9.6.1, May 2024

License

Commercial or Open Source

Open Source

GPL version 2

commercial

Bundled with Microsoft Office

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

FreeBSD
Linux
macOS
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

Fixed schema

yes

schema-free

yes

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

Typing

predefined data types such as float or date

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

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

Solr Parallel SQL Interface

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

Java API
RESTful HTTP/JSON API

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

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

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

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

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

Synchronous replication based on Galera library

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

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

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.