DBMS > dBASE vs. FatDB vs. Microsoft Azure Cosmos DB vs. SWC-DB

System Properties Comparison dBASE vs. FatDB vs. Microsoft Azure Cosmos DB vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Globally distributed, horizontally scalable, multi-model database service

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.dbase.com

azure.microsoft.com/services/cosmos-db

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.dbase.com/support/knowledgebase

learn.microsoft.com/azure/cosmos-db

Developer

Asthon Tate

FatCloud

Microsoft

Alex Kashirin

Initial release

1979

2012

2014

2020

Current release

dBASE 2019, 2019

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

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++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Windows

hosted

Linux

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

All properties auto-indexed by default

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Proprietary protocol
Thrift

Supported programming languages

dBase proprietary IDE

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

C++

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

via applications

JavaScript

Triggers

yes

via applications

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

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

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate 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

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

Can implement custom security layer via applications

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.