DBMS > Alibaba Cloud Table Store vs. dBASE vs. HEAVY.AI vs. SiteWhere vs. Snowflake

System Properties Comparison Alibaba Cloud Table Store vs. dBASE vs. HEAVY.AI vs. SiteWhere 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

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

M2M integration platform for persisting/querying time series data

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.24
Rank	#310	Overall
	#12	Wide column stores

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/table-store

www.dbase.com

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

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

www.dbase.com/support/knowledgebase

docs.heavy.ai

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Asthon Tate

HEAVY.AI, Inc.

SiteWhere

Snowflake Computing Inc.

Initial release

2016

1979

2016

2010

2014

Current release

dBASE 2019, 2019

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Common Public Attribution License Version 1.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

C++ and CUDA

Java

Server operating systems

hosted

DOS

dBase Classic
Windows

dBase Pro

Linux

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

predefined scheme

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

none

The IDE can access other DBMS or ODBC-sources.

JDBC
ODBC
Thrift
Vega

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

Java
Python

dBase proprietary IDE

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

none

Sharding

Round robin

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Multi-source replication

selectable replication factor

based on HBase

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

Atomic single-row operations

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

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.