DBMS > dBASE vs. EsgynDB vs. GeoSpock vs. Microsoft Azure Cosmos DB

System Properties Comparison dBASE vs. EsgynDB vs. GeoSpock vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial and temporal data processing engine for extreme data scale

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.dbase.com

www.esgyn.cn

geospock.com

azure.microsoft.com/services/cosmos-db

Technical documentation

www.dbase.com/support/knowledgebase

learn.microsoft.com/azure/cosmos-db

Developer

Asthon Tate

Esgyn

GeoSpock

Microsoft

Initial release

1979

2015

2014

Current release

dBASE 2019, 2019

2.0, September 2019

License

Commercial or Open Source

commercial

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

C++, Java

Java, Javascript

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC

JDBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

dBase proprietary IDE

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Java Stored Procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic sharding

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

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

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

Access rights can be defined down to the item level

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.