DBMS > Badger vs. ClickHouse vs. Datomic vs. FoundationDB vs. Microsoft Access

System Properties Comparison Badger vs. ClickHouse vs. Datomic vs. FoundationDB vs. Microsoft Access

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

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

Primary database model

Key-value store

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Website

github.com/dgraph-io/badger

clickhouse.com

www.datomic.com

github.com/apple/foundationdb

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

Technical documentation

godoc.org/github.com/dgraph-io/badger

clickhouse.com/docs

docs.datomic.com

apple.github.io/foundationdb

developer.microsoft.com/en-us/access

Developer

DGraph Labs

Clickhouse Inc.

Cognitect

FoundationDB

Microsoft

Initial release

2017

2016

2012

2013

1992

Current release

v23.12.1.1368-stable, December 2023

1.0.6735, June 2023

6.2.28, November 2020

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

limited edition free

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

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 Clickhouse: Managed cloud data warehousing with high-speed analytics.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

C++

Java, Clojure

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS

All OS with a Java VM

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

schema-free

yes

schema-free

some layers support schemas

yes

Typing

predefined data types such as float or date

yes

some layers support typing

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

Close to ANSI SQL (SQL/JSON + extensions)

supported in specific SQL layer only

yes

but not compliant to any SQL standard

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

Clojure
Java

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

Server-side scripts

Stored procedures

yes

Transaction Functions

in SQL-layer only

yes

since Access 2010 using the ACE-engine

Triggers

By using transaction functions

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

none

But extensive use of caching in the application peers

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Linearizable consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

but no files for transaction logging

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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

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.