DBMS > EsgynDB vs. FatDB vs. Google Cloud Datastore vs. MariaDB

System Properties Comparison EsgynDB vs. FatDB vs. Google Cloud Datastore vs. MariaDB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	93.81
Rank	#13	Overall
	#9	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/datastore

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

Technical documentation

cloud.google.com/datastore/docs

mariadb.com/kb/en/library

Developer

Esgyn

FatCloud

Google

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

The lead developer Monty Widenius is the original author of MySQL

Initial release

2015

2012

2008

2009

Fork of MySQL, which was first released in 1995

Current release

11.3.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial enterprise subscription available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

C and C++

Server operating systems

Linux

Windows

hosted

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Data scheme

yes

schema-free

yes

Dynamic columns are supported

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

Via inetgration in SQL Server

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

using Google App Engine

yes

PL/SQL compatibility added with version 10.3

Triggers

yes

via applications

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

several options for horizontal partitioning and Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

In-memory capabilities

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

yes

with MEMORY storage engine

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.