DBMS > Alibaba Cloud Table Store vs. Amazon Redshift vs. Faircom EDGE vs. Google Cloud Datastore vs. Linter

System Properties Comparison Alibaba Cloud Table Store vs. Amazon Redshift vs. Faircom EDGE vs. Google Cloud Datastore vs. Linter

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

Large scale data warehouse service for use with business intelligence tools

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDBMS for high security requirements

Primary database model

Wide column store

Relational DBMS

Key-value store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/redshift

www.faircom.com/products/faircom-edge

cloud.google.com/datastore

linter.ru

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/redshift

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

cloud.google.com/datastore/docs

Developer

Alibaba

Amazon (based on PostgreSQL)

FairCom Corporation

Google

relex.ru

Initial release

2016

2012

1979

2008

1990

Current release

V3, October 2020

License

Commercial or Open Source

commercial

Restricted, free version 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

ANSI C, C++

C and C++

Server operating systems

hosted

Android
Linux

ARM, x86
Raspbian
Windows

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes, details here

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

ANSI SQL queries

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP API

JDBC
ODBC

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

Java
Python

All languages supporting JDBC/ODBC

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

using Google App Engine

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic single-row operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

fine grained access rights according to SQL-standard

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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

fine grained access rights according to SQL-standard

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.