DBMS > AlaSQL vs. MariaDB vs. Oracle Berkeley DB vs. SingleStore vs. TerminusDB

System Properties Comparison AlaSQL vs. MariaDB vs. Oracle Berkeley DB vs. SingleStore vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

Document store
RDF store

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

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

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

alasql.org

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

www.singlestore.com

terminusdb.com

Technical documentation

github.com/AlaSQL/alasql

mariadb.com/kb/en/library

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

docs.singlestore.com

terminusdb.github.io/terminusdb/#

Developer

Andrey Gershun & Mathias R. Wulff

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

SingleStore Inc.

DataChemist Ltd.

Initial release

2014

2009

Fork of MySQL, which was first released in 1995

1994

2013

2018

Current release

11.3.2, February 2024

18.1.40, May 2020

8.5, January 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

commercial license available

commercial

free developer edition available

Open Source

GPL V3

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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

JavaScript

C and C++

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

C++, Go

Prolog, Rust

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

64 bit version required

Linux

Data scheme

schema-free

yes

Dynamic columns are supported

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

yes

but no triggers and foreign keys

SQL-like query language (WOQL)

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript

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

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

several options for horizontal partitioning and Sharding

none

Sharding

hash partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

not for in-memory storage engine

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes

in-memory journaling

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

User concepts

Access control

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

Role-based access control

More information provided by the system vendor

Specific characteristics

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

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

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

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

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

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

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

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

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

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

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

F ree Tier and Enterprise Edition
» 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.