DBMS > dBASE vs. EXASOL vs. Firebase Realtime Database vs. Hazelcast vs. Snowflake

System Properties Comparison dBASE vs. EXASOL vs. Firebase Realtime Database vs. Hazelcast 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.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A widely adopted in-memory data grid

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

Primary database model

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.16
Rank	#43	Overall
	#27	Relational DBMS

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.dbase.com

www.exasol.com

firebase.google.com/products/realtime-database

hazelcast.com

www.snowflake.com

Technical documentation

www.dbase.com/support/knowledgebase

www.exasol.com/resources

firebase.google.com/docs/database

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Exasol

Google

acquired by Google 2014

Hazelcast

Snowflake Computing Inc.

Initial release

1979

2000

2012

2008

2014

Current release

dBASE 2019, 2019

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

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

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

All OS with a Java VM

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

Android
iOS
JavaScript API
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

Java
Lua
Python
R

Java
JavaScript
Objective-C

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

limited functionality with using 'rules'

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Callbacks are triggered when data changes

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

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

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

yes, based on authentication and database rules

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.