DBMS > BigchainDB vs. dBASE vs. HEAVY.AI vs. OpenQM vs. Snowflake

System Properties Comparison BigchainDB vs. dBASE vs. HEAVY.AI vs. OpenQM vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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 high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.bigchaindb.com

www.dbase.com

github.com/heavyai/heavydb
www.heavy.ai

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

docs.heavy.ai

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

HEAVY.AI, Inc.

Rocket Software, originally Martin Phillips

Snowflake Computing Inc.

Initial release

2016

1979

2016

1993

2014

Current release

dBASE 2019, 2019

5.10, January 2022

3.4-12

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

GPLv2, extended commercial license 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.

Implementation language

Python

C++ and CUDA

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Data scheme

schema-free

yes

with some exceptions

yes

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

Typing

predefined data types such as float or date

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

yes

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.