DBMS > ClickHouse vs. dBASE vs. Geode vs. Google Cloud Bigtable vs. IBM Db2

System Properties Comparison ClickHouse vs. dBASE vs. Geode vs. Google Cloud Bigtable vs. IBM Db2

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Primary database model

Relational DBMS

Key-value store

Key-value store
Wide column store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Secondary database models

Time Series DBMS

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	1.86
Rank	#134	Overall
	#24	Key-value stores

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

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Website

clickhouse.com

www.dbase.com

geode.apache.org

cloud.google.com/bigtable

www.ibm.com/products/db2

Technical documentation

clickhouse.com/docs

www.dbase.com/support/knowledgebase

geode.apache.org/docs

cloud.google.com/bigtable/docs

www.ibm.com/docs/en/db2

Developer

Clickhouse Inc.

Asthon Tate

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

IBM

Initial release

2016

1979

2002

2015

1983

host version

Current release

v24.4.1.2088-stable, May 2024

dBASE 2019, 2019

1.1, February 2017

12.1, October 2016

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free version is 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.

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

Java

C and C++

Server operating systems

FreeBSD
Linux
macOS

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

the JDK (8 or later) is also required

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

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)

SQL-like query language (OQL)

yes

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.

Java Client API
Memcached protocol
RESTful HTTP API

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

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

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

The IDE can access stored procedures in other database systems.

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

only with Windows/Unix/Linux Version

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Multi-source replication

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

yes

with separate tools (MQ, InfoSphere)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

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

yes, on a single node

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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 per client and object definable

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

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.