DBMS > dBASE vs. Firebird vs. Redis vs. Spark SQL

System Properties Comparison dBASE vs. Firebird vs. Redis vs. Spark SQL

Please select another system to include it in the comparison.

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.

Firebird is an open source RDBMS forked from Borland's InterBase

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	156.44
Rank	#6	Overall
	#1	Key-value stores

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

www.firebirdsql.org/en/reference-manuals

docs.redis.com/latest/index.html
redis.io/docs

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Asthon Tate

Firebird Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation

Initial release

1979

2000

As fork of Borland's InterBase

2009

2014

Current release

dBASE 2019, 2019

5.0.0, January 2024

7.2.4, January 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C and C++

Scala

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

with RediSearch module

SQL

Support of SQL

yes

with RediSQL module

SQL-like DML and DDL statements

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC

Supported programming languages

dBase proprietary IDE

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Java
Python
R
Scala

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

PSQL

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

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 execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Users with fine-grained authorization concept

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based 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.