DBMS > dBASE vs. GeoMesa vs. Riak KV vs. STSdb

System Properties Comparison dBASE vs. GeoMesa vs. Riak KV vs. STSdb

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

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

Key-value store

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

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

www.dbase.com

www.geomesa.org

github.com/STSSoft/STSdb4

Technical documentation

www.dbase.com/support/knowledgebase

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

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

Developer

Asthon Tate

CCRi and others

OpenSource, formerly Basho Technologies

STS Soft SC

Initial release

1979

2014

2009

2011

Current release

dBASE 2019, 2019

4.0.5, February 2024

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

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

Linux
OS X

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

HTTP API
Native Erlang Interface

.NET Client API

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

C#
Java

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"

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

selectable replication factor

none

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

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

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

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

DBF File (What It Is and How to Open One)
6 April 2023, Lifewire

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

What is Dbase? - Definition from Techopedia
19 September 2011, Techopedia

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page