DBMS > dBASE vs. Drizzle vs. EXASOL vs. Google Cloud Bigtable vs. RocksDB

System Properties Comparison dBASE vs. Drizzle vs. EXASOL vs. Google Cloud Bigtable vs. RocksDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store
Wide column store

Key-value store

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.dbase.com

www.exasol.com

cloud.google.com/bigtable

rocksdb.org

Technical documentation

www.dbase.com/support/knowledgebase

www.exasol.com/resources

cloud.google.com/bigtable/docs

github.com/facebook/rocksdb/wiki

Developer

Asthon Tate

Drizzle project, originally started by Brian Aker

Exasol

Google

Facebook, Inc.

Initial release

1979

2008

2000

2015

2013

Current release

dBASE 2019, 2019

7.2.4, September 2012

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Open Source

BSD

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.

Implementation language

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X

hosted

Linux

Data scheme

yes

schema-free

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

yes

with proprietary extensions

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JDBC

.Net
JDBC
ODBC
WebSocket

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

C++ API
Java API

Supported programming languages

dBase proprietary IDE

C
C++
Java
PHP

Java
Lua
Python
R

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

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)

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

ACID

Atomic single-row operations

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles according to SQL-standard

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

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.