DBMS > BigObject vs. Faircom DB vs. Linter vs. MariaDB vs. MarkLogic

System Properties Comparison BigObject vs. Faircom DB vs. Linter vs. MariaDB vs. MarkLogic

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

RDBMS for high security requirements

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.

Operational and transactional Enterprise NoSQL database

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store
Relational DBMS

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Website

bigobject.io

www.faircom.com/products/faircom-db

linter.ru

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.marklogic.com

Technical documentation

docs.bigobject.io

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

mariadb.com/kb/en/library

docs.marklogic.com

Developer

BigObject, Inc.

FairCom Corporation

relex.ru

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

The lead developer Monty Widenius is the original author of MySQL

MarkLogic Corp.

Initial release

2015

1979

1990

2009

Fork of MySQL, which was first released in 1995

2001

Current release

V12, November 2020

11.3.2, February 2024

11.0, December 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

Restricted, free version available

commercial

Open Source

GPL version 2, commercial enterprise subscription available

commercial

restricted free version is 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

ANSI C, C++

C and C++

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Linux
OS X
Windows

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

Dynamic columns are supported

schema-free

Schema can be enforced

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

yes

SQL92

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

.Net, JavaScript, C/C++

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

PL/SQL compatibility added with version 10.3

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

several options for horizontal partitioning and Sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

not for MyISAM storage engine

ACID

can act as a resource manager in an XA/JTA transaction

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

yes

not for in-memory storage engine

yes

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, with Range Indexes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.