DBMS > Alibaba Cloud Table Store vs. Apache Phoenix vs. BigchainDB vs. dBASE vs. Snowflake

System Properties Comparison Alibaba Cloud Table Store vs. Apache Phoenix vs. BigchainDB vs. dBASE vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

A scale-out RDBMS with evolutionary schema built on Apache HBase

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.

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

Primary database model

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/table-store

Technical documentation

www.alibabacloud.com/help/en/tablestore

phoenix.apache.org

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Apache Software Foundation

Asthon Tate

Snowflake Computing Inc.

Initial release

2016

2014

2016

1979

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

dBASE 2019, 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL v3

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

Python

Server operating systems

hosted

Linux
Unix
Windows

Linux

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

schema-free

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

HTTP API

JDBC

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

CLI Client
JDBC
ODBC

Supported programming languages

Java
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-row operations

ACID

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

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

Access rights based on subaccounts and tokens

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

Access rights for users and 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.