DBMS > dBASE vs. Google Cloud Bigtable vs. Microsoft Azure Data Explorer vs. RocksDB

System Properties Comparison dBASE vs. Google Cloud Bigtable vs. Microsoft Azure Data Explorer vs. RocksDB

Please select another system to include it in the comparison.

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Fully managed big data interactive analytics platform

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

column oriented

Key-value store

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.dbase.com

cloud.google.com/bigtable

azure.microsoft.com/services/data-explorer

rocksdb.org

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigtable/docs

docs.microsoft.com/en-us/azure/data-explorer

github.com/facebook/rocksdb/wiki

Developer

Asthon Tate

Google

Microsoft

Facebook, Inc.

Initial release

1979

2015

2019

2013

Current release

dBASE 2019, 2019

cloud service with continuous releases

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

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

hosted

Linux

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-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.

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

C++ API
Java API

Supported programming languages

dBase proprietary IDE

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Yes, possible languages: KQL, Python, R

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual 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

Atomic single-row operations

yes

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.

yes

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Azure Active Directory 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.