DBMS > BigObject vs. FatDB vs. Microsoft Access vs. WakandaDB

System Properties Comparison BigObject vs. FatDB vs. Microsoft Access vs. WakandaDB

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

Analytic DBMS for real-time computations and queries

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.)

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Key-value store

Relational DBMS

Object oriented DBMS

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

Score	0.13
Rank	#342	Overall
	#150	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.09
Rank	#352	Overall
	#16	Object oriented DBMS

Website

bigobject.io

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

wakanda.github.io

Technical documentation

docs.bigobject.io

developer.microsoft.com/en-us/access

wakanda.github.io/doc

Developer

BigObject, Inc.

FatCloud

Microsoft

Wakanda SAS

Initial release

2015

2012

1992

2012

Current release

1902 (16.0.11328.20222), March 2019

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

free community edition available

commercial

Bundled with Microsoft Office

Open Source

AGPLv3, extended commercial license available

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.

Implementation language

C++

C++, JavaScript

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Via inetgration in SQL Server

yes

but not compliant to any SQL standard

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

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

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

Supported programming languages

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

JavaScript

Server-side scripts

Stored procedures

Lua

yes

via applications

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

via applications

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MS Access drops in DB-Engines Ranking
2 May 2013, Paul Andlinger

Microsoft SQL Server regained rank 2 in the DB-Engines popularity ranking
3 December 2012, Matthias Gelbmann

New DB-Engines Ranking shows the popularity of database management systems
3 October 2012, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Abusing Microsoft Access "Linked Table" Feature to Perform NTLM Forced Authentication Attacks
9 November 2023, Check Point Research

MS access program to increase awareness and independence of those living with MS and disability
10 July 2023, Nebraska Medicine

Hackers Exploit Microsoft Access Feature to Steal Windows User’s NTLM Tokens
11 November 2023, CybersecurityNews

After installing Navisworks, Office 2016 (32-bit) applications stopped launching
8 October 2023, Autodesk Redshift

ACCDE File (What It Is and How to Open One)
27 July 2023, Lifewire

provided by Google News

Share this page