DBMS > FoundationDB vs. GraphDB vs. IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB

System Properties Comparison FoundationDB vs. GraphDB vs. IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Ordered key-value store. Core features are complimented by layers.

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Database as a Service offering based on Apache CouchDB

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Graph DBMS
RDF store

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	3.32
Rank	#91	Overall
	#6	Graph DBMS
	#4	RDF stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

github.com/apple/foundationdb

www.ontotext.com

www.ibm.com/products/cloudant

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

azure.microsoft.com/services/cosmos-db

Technical documentation

apple.github.io/foundationdb

graphdb.ontotext.com/documentation

cloud.ibm.com/docs/Cloudant

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

Social network pages

Developer

FoundationDB

Ontotext

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2013

2000

2010

1992

2014

Current release

6.2.28, November 2020

10.4, October 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

Bundled with Microsoft Office

commercial

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

Erlang

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM
Linux
OS X
Windows

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

some layers support schemas

schema-free and OWL/RDFS-schema support; RDF shapes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

some layers support typing

yes

JSON types

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, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

supported in specific SQL layer only

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

in SQL-layer only

well-defined plugin interfaces; JavaScript server-side extensibility

View functions (Map-Reduce) in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication
Source-replica replication

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Constraint checking

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

User concepts

Access control

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

Access rights for users can be defined per database

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

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Case study: Policy Enforcement Automation With Semantics
2 May 2024

Okay, RAG… We Have a Problem
26 April 2024

Scaling Understanding with the Help of Feedback Loops, Knowledge Graphs and NLP
19 April 2024

How Knowledge Graphs Power Data Mesh and Data Fabric
10 April 2024

Building Smarter Financial Services: The Role of Semantic Technologies, Knowledge Graphs and Generative AI
3 April 2024

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.