DBMS > BigObject vs. dBASE vs. GeoMesa vs. Vitess

System Properties Comparison BigObject vs. dBASE vs. GeoMesa vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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.

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

docs.bigobject.io

www.dbase.com/support/knowledgebase

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

vitess.io/docs

Developer

BigObject, Inc.

Asthon Tate

CCRi and others

The Linux Foundation, PlanetScale

Initial release

2015

1979

2014

2013

Current release

dBASE 2019, 2019

4.0.5, February 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

DOS

dBase Classic
Windows

dBase Pro

Docker
Linux
macOS

Data scheme

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

dBase proprietary IDE

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Lua

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

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

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

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

Liam Brady's wife and their family life with three children
20 October 2023, Irish Mirror

provided by Google News

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

The ultimate MySQL database platform — PlanetScale
20 June 2018, planetscale.com

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page