DBMS > Faircom DB vs. MaxDB vs. MySQL vs. Solr

System Properties Comparison Faircom DB vs. MaxDB vs. MySQL vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used open source RDBMS

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

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.faircom.com/products/faircom-db

maxdb.sap.com

www.mysql.com

solr.apache.org

Technical documentation

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

maxdb.sap.com/documentation

dev.mysql.com/doc

solr.apache.org/resources.html

Developer

FairCom Corporation

SAP, acquired from Software AG (Adabas-D) in 1997

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

1979

1984

1995

2006

Current release

V12, November 2020

7.9.10.12, February 2024

8.4.0, April 2024

9.6.0, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Limited community edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

ANSI C, C++

C++

C and C++

Java

Server operating systems

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

easily portable to other OSs

AIX
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

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

Data scheme

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

yes

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

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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, ANSI SQL with proprietary extensions

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

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

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RESTful HTTP/JSON API

Supported programming languages

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

.Net
C#
Java
Perl
PHP
Python

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

.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

.Net, JavaScript, C/C++

yes

proprietary syntax

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

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

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.