DBMS > AlaSQL vs. ClickHouse vs. FoundationDB vs. GeoMesa vs. MySQL

System Properties Comparison AlaSQL vs. ClickHouse vs. FoundationDB vs. GeoMesa vs. MySQL

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

JavaScript DBMS library

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational 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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

alasql.org

clickhouse.com

github.com/apple/foundationdb

www.geomesa.org

www.mysql.com

Technical documentation

github.com/AlaSQL/alasql

clickhouse.com/docs

apple.github.io/foundationdb

www.geomesa.org/documentation/stable/user/index.html

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Clickhouse Inc.

FoundationDB

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2016

2013

2014

1995

Current release

v24.4.1.2088-stable, May 2024

6.2.28, November 2020

5.0.0, May 2024

8.4.0, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

JavaScript

C++

Scala

C and C++

Server operating systems

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

FreeBSD
Linux
macOS

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

Close to ANSI SQL (SQL/JSON + extensions)

supported in specific SQL layer only

yes

with proprietary extensions

APIs and other access methods

JavaScript API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

in SQL-layer only

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

Sharding

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

yes

depending on storage layer

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Linearizable consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

in SQL-layer only

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

In-memory capabilities

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

yes

depending on storage layer

yes

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.

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

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.