DBMS > dBASE vs. EXASOL vs. Hazelcast vs. RocksDB vs. Snowflake

System Properties Comparison dBASE vs. EXASOL vs. Hazelcast vs. RocksDB vs. Snowflake

Editorial information provided by DB-Engines

Name

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.

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

A widely adopted in-memory data grid

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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	5.46
Rank	#61	Overall
	#7	Key-value stores

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

www.exasol.com/resources

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Exasol

Hazelcast

Facebook, Inc.

Snowflake Computing Inc.

Initial release

1979

2000

2008

2013

2014

Current release

dBASE 2019, 2019

5.3.6, November 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

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

Java

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

Linux

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

Java
Lua
Python
R

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

C
C++
Go
Java
Perl
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate 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

ACID

one or two-phase-commit; repeatable reads; read commited

yes

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

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

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.