DBMS > Faircom DB vs. FileMaker vs. Microsoft Access vs. MongoDB vs. Vertica

System Properties Comparison Faircom DB vs. FileMaker vs. Microsoft Access vs. MongoDB vs. Vertica

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

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

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

Spatial DBMS
Time Series DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	421.65
Rank	#5	Overall
	#1	Document stores

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.claris.com/filemaker

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

www.mongodb.com

www.vertica.com

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.claris.com/resources/documentation

developer.microsoft.com/en-us/access

www.mongodb.com/docs/manual

vertica.com/documentation

Developer

FairCom Corporation

Claris

a subsidiary of Apple

Microsoft

MongoDB, Inc

OpenText

previously Micro Focus and Hewlett Packard

Initial release

1979

1983

1992

2009

2005

Current release

V12, November 2020

19.4.1, November 2021

1902 (16.0.11328.20222), March 2019

6.0.7, June 2023

12.0.3, January 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Bundled with Microsoft Office

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

MongoDB Atlas: Global multi-cloud database with unmatched data distribution and mobility across AWS, Azure, and Google Cloud, built-in automation for resource and workload optimization, and so much more.
MongoDB Flex @ STACKIT offers managed MongoDB Instances with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

ANSI C, C++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema free, schema optional, schema required, partial schema,

yes

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

A http query request can return the data in XML format

Secondary indexes

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

via plugins

yes

but not compliant to any SQL standard

Read-only SQL queries via the MongoDB Atlas SQL Interface

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Filemaker WebDirect
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

PHP

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

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

since Access 2010 using the ACE-engine

JavaScript

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

since Access 2010 using the ACE-engine

yes

in MongoDB Atlas only

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication, warm standby

since Version 14

none

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

but no files for transaction logging

Multi-document ACID Transactions with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

but no files for transaction logging

yes

optional, enabled by default

yes

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

simple rights management via user accounts and connection to external directory services

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

Access rights for users and roles

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

MongoDB provides an integrated suite of cloud database and data services to accelerate...
» more

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Built around the flexible document data model and unified API, MongoDB is a developer...
» more

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

AI-enriched intelligent apps (Continental, Telefonica, Iron Mountain) Internet of...
» more

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

ADP, Adobe, Amadeus, AstraZeneca, Auto Trader, Barclays, BBVA, Bosch, Cisco, CERN,...
» more

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Market metrics

Hundreds of millions downloads, over 150,000+ Atlas clusters provisioned every month...
» more

Licensing and pricing models

MongoDB database server: Server-Side Public License (SSPL) . Commercial licenses...
» more

Cost-based models and subscription-based models are both available. One license is...
» 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.