DBMS > MariaDB vs. Oracle Berkeley DB vs. Oracle NoSQL vs. Solr vs. Tarantool

System Properties Comparison MariaDB vs. Oracle Berkeley DB vs. Oracle NoSQL vs. Solr vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Widely used in-process key-value store

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Key-value store
Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

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

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.oracle.com/database/technologies/related/berkeleydb.html

www.oracle.com/database/nosql/technologies/nosql

solr.apache.org

www.tarantool.io

Technical documentation

mariadb.com/kb/en/library

docs.oracle.com/cd/E17076_05/html/index.html

docs.oracle.com/en/database/other-databases/nosql-database/index.html

solr.apache.org/resources.html

www.tarantool.io/en/doc

Developer

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle

Apache Software Foundation

Initial release

2009

Fork of MySQL, which was first released in 1995

1994

2011

2006

2008

Current release

11.3.2, February 2024

18.1.40, May 2020

23.3, December 2023

9.5.0, February 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

commercial license available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Apache Version 2

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

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Java

C and C++

Server operating systems

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Solaris SPARC/x86

All OS with a Java VM

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

BSD
Linux
macOS

Data scheme

yes

Dynamic columns are supported

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

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

optional

yes

supports customizable data types and automatic typing

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.

yes

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

SQL-like DML and DDL statements

Solr Parallel SQL Interface

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Open binary protocol

Supported programming languages

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C#
Go
Java
JavaScript (Node.js)
Python

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

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

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

Java plugins

Lua, C and SQL stored procedures

Triggers

yes

only for the SQL API

yes

User configurable commands triggered on index changes

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

Partitioning methods

Methods for storing different data on different nodes

several options for horizontal partitioning and Sharding

none

Sharding

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

Multi-source replication
Source-replica replication

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

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

with Hadoop integration

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual 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

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

configurable

ACID within a storage node (=shard)

optimistic locking

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

not for in-memory storage engine

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

with MEMORY storage engine

yes

off heap cache

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

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

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.