DBMS > FatDB vs. Microsoft Access vs. Spark SQL vs. YugabyteDB

System Properties Comparison FatDB vs. Microsoft Access vs. Spark SQL vs. YugabyteDB

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

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Wide column store

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

Score	143.44
Rank	#9	Overall
	#6	Relational DBMS

Score	22.86
Rank	#35	Overall
	#21	Relational DBMS

Score	2.68
Rank	#112	Overall
	#57	Relational DBMS

Website

www.microsoft.com/en-us/microsoft-365/access

spark.apache.org/sql

www.yugabyte.com

Technical documentation

developer.microsoft.com/en-us/access

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

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

FatCloud

Microsoft

Apache Software Foundation

Yugabyte Inc.

Initial release

2012

1992

2014

2017

Current release

1902 (16.0.11328.20222), March 2019

3.2.0, October 2021

2.6, August 2021

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache 2.0

Open Source

Apache 2.0

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.

Yugabyte Cloud is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

C++

Scala

C and C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Linux
OS X

Data scheme

schema-free

yes

depending on used data model

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.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements

yes, PostgreSQL compatible

APIs and other access methods

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

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Java
Python
R
Scala

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

Server-side scripts

Stored procedures

yes

via applications

yes

since Access 2010 using the ACE-engine

yes

sql, plpgsql, C

Triggers

yes

via applications

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, utilizing Spark Core

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

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

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

based on RocksDB

In-memory capabilities

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

User concepts

Access control

Can implement custom security layer via applications

a simple user-level security was built in till version Access 2003

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

900,000+ lifetime clusters deployed 5.5K+ GitHub stars 4.3K+ YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» 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.