DBMS > dBASE vs. EventStoreDB vs. Hyprcubd vs. MySQL vs. Snowflake

System Properties Comparison dBASE vs. EventStoreDB vs. Hyprcubd vs. MySQL vs. Snowflake

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is 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.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Serverless Time Series DBMS

Widely used open source RDBMS

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.dbase.com

www.eventstore.com

hyprcubd.com (offline)

www.mysql.com

www.snowflake.com

Technical documentation

www.dbase.com/support/knowledgebase

developers.eventstore.com

dev.mysql.com/doc

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Event Store Limited

Hyprcubd, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Snowflake Computing Inc.

Initial release

1979

2012

1995

2014

Current release

dBASE 2019, 2019

21.2, February 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

gRPC (https)

ADO.NET
JDBC
ODBC
Proprietary native API

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

token access

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable 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.