DBMS > FatDB vs. MySQL vs. RavenDB vs. Spark SQL vs. TigerGraph

System Properties Comparison FatDB vs. MySQL vs. RavenDB vs. Spark SQL vs. TigerGraph

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

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

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Spark SQL is a component on top of 'Spark Core' for structured data processing

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

Technical documentation

dev.mysql.com/doc

ravendb.net/docs

spark.apache.org/docs/latest/sql-programming-guide.html

docs.tigergraph.com

Developer

FatCloud

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Apache Software Foundation

Initial release

2012

1995

2010

2014

2017

Current release

8.4.0, April 2024

5.4, July 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

Open Source

Apache 2.0

commercial

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++

Scala

C++

Server operating systems

Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

with proprietary extensions

SQL-like query language (RQL)

SQL-like DML and DDL statements

SQL-like query language (GSQL)

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

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

Java
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

ACID

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

User concepts

Access control

Can implement custom security layer via applications

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

Role-based access control

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.