DBMS > ClickHouse vs. Dragonfly vs. Google Cloud Datastore vs. Interbase vs. Microsoft Access

System Properties Comparison ClickHouse vs. Dragonfly vs. Google Cloud Datastore vs. Interbase vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Description

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.

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Light-weight proven RDBMS

originally from Borland

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

Secondary database models

Time Series DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

clickhouse.com

github.com/dragonflydb/dragonfly
www.dragonflydb.io

cloud.google.com/datastore

www.embarcadero.com/products/interbase

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

Technical documentation

clickhouse.com/docs

www.dragonflydb.io/docs

cloud.google.com/datastore/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

Developer

Clickhouse Inc.

DragonflyDB team and community contributors

Google

Embarcadero

Microsoft

Initial release

2016

2023

2008

1984

1992

Current release

v24.4.1.2088-stable, May 2024

1.0, March 2023

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSL 1.1

commercial

Bundled with Microsoft Office

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.

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 Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Server operating systems

FreeBSD
Linux
macOS

Linux

hosted

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

yes, details here

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

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

Proprietary protocol

RESP - REdis Serialization Protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

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

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

Server-side scripts

Stored procedures

yes

Lua

using Google App Engine

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

publish/subscribe channels provide some trigger functionality

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

Multi-source replication using Paxos

Interbase Change Views

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

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

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.

Password-based authentication

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.