DBMS > dBASE vs. InterSystems Caché vs. RavenDB vs. RocksDB

System Properties Comparison dBASE vs. InterSystems Caché vs. RavenDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed 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.

A multi-model DBMS and application server

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Document store

Key-value store

Secondary database models

Document store

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

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

Website

www.dbase.com

www.intersystems.com/products/cache

ravendb.net

rocksdb.org

Technical documentation

www.dbase.com/support/knowledgebase

docs.intersystems.com

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Asthon Tate

InterSystems

Hibernating Rhinos

Facebook, Inc.

Initial release

1979

1997

2010

2013

Current release

dBASE 2019, 2019

2018.1.4, May 2020

5.4, July 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

BSD

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.

Implementation language

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

depending on used data model

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.NET Client API
JDBC
ODBC
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

dBase proprietary IDE

C#
C++
Java

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

Triggers

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

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

Access rights for users, groups and roles

Authorization levels configured per client per database

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.