DBMS > atoti vs. Blueflood vs. dBASE vs. Microsoft Azure Cosmos DB

System Properties Comparison atoti vs. Blueflood vs. dBASE vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Object oriented DBMS

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.59
Rank	#242	Overall
	#10	Object oriented DBMS

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

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

Website

atoti.io

blueflood.io

www.dbase.com

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.atoti.io

github.com/rax-maas/blueflood/wiki

www.dbase.com/support/knowledgebase

learn.microsoft.com/azure/cosmos-db

Developer

ActiveViam

Rackspace

Asthon Tate

Microsoft

Initial release

2013

1979

2014

Current release

dBASE 2019, 2019

License

Commercial or Open Source

commercial

free versions available

Open Source

Apache 2.0

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

hosted

Data scheme

predefined 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

Multidimensional Expressions (MDX)

SQL-like query language

APIs and other access methods

HTTP REST

none

The IDE can access other DBMS or ODBC-sources.

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

Supported programming languages

dBase proprietary IDE

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

Server-side scripts

Stored procedures

Python

The IDE can access stored procedures in other database systems.

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

based on Cassandra

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

Implicit feature of the cloud service

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

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, multi-version concurrency control (MVCC)

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

User concepts

Access control

Access rights for users and roles

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.