DBMS > BigObject vs. dBASE vs. GeoMesa vs. Google BigQuery vs. Heroic

System Properties Comparison BigObject vs. dBASE vs. GeoMesa vs. Google BigQuery vs. Heroic

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.

Large scale data warehouse service with append-only tables

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Website

bigobject.io

www.dbase.com

www.geomesa.org

cloud.google.com/bigquery

github.com/spotify/heroic

Technical documentation

docs.bigobject.io

www.dbase.com/support/knowledgebase

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

cloud.google.com/bigquery/docs

spotify.github.io/heroic

Developer

BigObject, Inc.

Asthon Tate

CCRi and others

Google

Spotify

Initial release

2015

1979

2014

2010

2014

Current release

dBASE 2019, 2019

5.0.0, May 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java

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

hosted

Data scheme

yes

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

via Elasticsearch

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

depending on storage layer

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.