DBMS > BaseX vs. ClickHouse vs. FoundationDB vs. Lovefield vs. RavenDB

System Properties Comparison BaseX vs. ClickHouse vs. FoundationDB vs. Lovefield vs. RavenDB

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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.

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

Embeddable relational database for web apps written in pure JavaScript

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Native XML DBMS

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

basex.org

clickhouse.com

github.com/apple/foundationdb

google.github.io/lovefield

ravendb.net

Technical documentation

docs.basex.org

clickhouse.com/docs

apple.github.io/foundationdb

github.com/google/lovefield/blob/master/docs/spec_index.md

ravendb.net/docs

Developer

BaseX GmbH

Clickhouse Inc.

FoundationDB

Google

Hibernating Rhinos

Initial release

2007

2016

2013

2014

2010

Current release

11.0, June 2024

v24.4.2.141-stable, June 2024

6.2.28, November 2020

2.1.12, February 2017

5.4, July 2022

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3, 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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

Java

C++

JavaScript

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

some layers support schemas

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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

SQL-like query language

via JavaScript builder pattern

SQL-like query language (RQL)

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

in SQL-layer only

yes

Triggers

yes

via events

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

yes

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

multiple readers, single writer

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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.

Authorization levels configured per client per database

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.