DBMS > dBASE vs. GeoMesa vs. Lovefield vs. Snowflake vs. SQL.JS

System Properties Comparison dBASE vs. GeoMesa vs. Lovefield vs. Snowflake vs. SQL.JS

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.

Embeddable relational database for web apps written in pure JavaScript

Cloud-based data warehousing service for structured and semi-structured data

Port of SQLite to JavaScript

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

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	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

www.dbase.com

www.geomesa.org

google.github.io/lovefield

www.snowflake.com

sql.js.org

Technical documentation

www.dbase.com/support/knowledgebase

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

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

Developer

Asthon Tate

CCRi and others

Google

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

Initial release

1979

2014

2012

Current release

dBASE 2019, 2019

5.0.0, May 2024

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

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

JavaScript

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

CLI Client
JDBC
ODBC

JavaScript API

Supported programming languages

dBase proprietary IDE

JavaScript

JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

none

yes

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

Immediate Consistency

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

except by serializing a db to a file

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

using MemoryDB

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, user roles and pluggable authentication

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.