DBMS > DataFS vs. FatDB vs. MySQL vs. Percona Server for MongoDB

System Properties Comparison DataFS vs. FatDB vs. MySQL vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Widely used open source RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Object oriented DBMS

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Graph DBMS

Document store
Spatial DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

newdatabase.com

www.mysql.com

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

dev.mobiland.com/Overview.xsp

dev.mysql.com/doc

docs.percona.com/percona-distribution-for-mongodb

Developer

Mobiland AG

FatCloud

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Initial release

2018

2012

1995

2015

Current release

1.1.263, October 2022

8.4.0, April 2024

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL 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

C and C++

C++

Server operating systems

Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

schema-free

yes

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Supported programming languages

.Net
C
C#
C++
VB.Net

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

JavaScript

Triggers

no, except callback-events from server when changes happened

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

User concepts

Access control

Windows-Profile

Can implement custom security layer via applications

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.