DBMS > ClickHouse vs. dBASE vs. Google Cloud Bigtable vs. Google Cloud Firestore vs. IBM Db2 Event Store

System Properties Comparison ClickHouse vs. dBASE vs. Google Cloud Bigtable vs. Google Cloud Firestore vs. IBM Db2 Event Store

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.

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Distributed Event Store optimized for Internet of Things use cases

Primary database model

Relational DBMS

Key-value store
Wide column store

Document store

Event Store
Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Website

clickhouse.com

www.dbase.com

cloud.google.com/bigtable

firebase.google.com/products/firestore

www.ibm.com/products/db2-event-store

Technical documentation

clickhouse.com/docs

www.dbase.com/support/knowledgebase

cloud.google.com/bigtable/docs

firebase.google.com/docs/firestore

www.ibm.com/docs/en/db2-event-store

Developer

Clickhouse Inc.

Asthon Tate

Google

IBM

Initial release

2016

1979

2015

2017

Current release

v24.4.2.141-stable, June 2024

dBASE 2019, 2019

2.0

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free developer edition available

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.

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

Implementation language

C++

C and C++

Server operating systems

FreeBSD
Linux
macOS

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux

Linux, macOS, Windows for the developer addition

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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)

yes

through the embedded Spark runtime

APIs and other access methods

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

none

The IDE can access other DBMS or ODBC-sources.

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

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

dBase proprietary IDE

C#
C++
Go
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Server-side scripts

Stored procedures

yes

The IDE can access stored procedures in other database systems.

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication

Active-active shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

Atomic single-row operations

yes

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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.

Access rights for users and roles

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

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.