DBMS > dBASE vs. GeoMesa vs. Oracle Rdb vs. Riak KV

System Properties Comparison dBASE vs. GeoMesa vs. Oracle Rdb vs. Riak KV

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.dbase.com

www.geomesa.org

www.oracle.com/database/technologies/related/rdb.html

Technical documentation

www.dbase.com/support/knowledgebase

www.geomesa.org/documentation/stable/user/index.html

www.oracle.com/database/technologies/related/rdb-doc.html

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Asthon Tate

CCRi and others

Oracle, originally developed by Digital Equipment Corporation (DEC)

OpenSource, formerly Basho Technologies

Initial release

1979

2014

1984

2009

Current release

dBASE 2019, 2019

5.0.0, May 2024

7.4.1.1, 2021

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Scala

Erlang

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

HP Open VMS

Linux
OS X

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

HTTP API
Native Erlang Interface

Supported programming languages

dBase proprietary IDE

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

yes, on a single node

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.

depending on storage layer

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

yes, using Riak Security

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

DB-Engines Ranking coverage expanded to 169 database management systems
3 June 2013, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

AIHA and dBase Media Launch Season Two of Healthier Workplaces, A Healthier World, an Occupational and ...
13 June 2024, Business Wire

30 Years Ago: The Rise, Fall and Survival of Ashton-Tate's dBASE
19 September 2013, eWeek

Microsoft Access 2016 Now Supports dBase Database Format
7 September 2016, Redmondmag.com

A malicious document could lead to RCE in Apache OpenOffice (CVE-2021-33035)
22 September 2021, Help Net Security

WFP DBase (Logistics Data, Budgets and Systems Execution) Factsheet (November 2019) - World
23 December 2019, ReliefWeb

provided by Google News

Oracle Adds New AI-Enabling Features To MySQL HeatWave
23 March 2023, Forbes

Should we all consolidate databases for the storage benefits? Reg vultures deploy DevOps, zoos, haircuts
18 September 2020, The Register

2013 Data Science Salary Survey – O'Reilly
4 May 2013, O'Reilly Media

provided by Google News

Share this page