DBMS > Blueflood vs. dBASE vs. EJDB vs. Microsoft Azure Cosmos DB vs. PlanetScale

System Properties Comparison Blueflood vs. dBASE vs. EJDB vs. Microsoft Azure Cosmos DB vs. PlanetScale

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Globally distributed, horizontally scalable, multi-model database service

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Time Series DBMS

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

blueflood.io

www.dbase.com

github.com/Softmotions/ejdb

azure.microsoft.com/services/cosmos-db

planetscale.com

Technical documentation

github.com/rax-maas/blueflood/wiki

www.dbase.com/support/knowledgebase

github.com/Softmotions/ejdb/blob/master/README.md

learn.microsoft.com/azure/cosmos-db

planetscale.com/docs

Developer

Rackspace

Asthon Tate

Softmotions

Microsoft

PlanetScale

Initial release

2013

1979

2012

2014

2020

Current release

dBASE 2019, 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPLv2

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

Java

Server operating systems

Linux
OS X

DOS

dBase Classic
Windows

dBase Pro

server-less

hosted

Docker
Linux
macOS

Data scheme

predefined scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

HTTP REST

none

The IDE can access other DBMS or ODBC-sources.

in-process shared library

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

dBase proprietary IDE

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

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

The IDE can access stored procedures in other database systems.

JavaScript

yes

proprietary syntax

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

User concepts

Access control

Access rights for users and roles

Access rights can be defined down to the item level

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.