DBMS > Alibaba Cloud Table Store vs. Google BigQuery vs. Ignite vs. Teradata Aster

System Properties Comparison Alibaba Cloud Table Store vs. Google BigQuery vs. Ignite vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Large scale data warehouse service with append-only tables

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Platform for big data analytics on multistructured data sources and types

Primary database model

Wide column store

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

www.alibabacloud.com/product/table-store

cloud.google.com/bigquery

ignite.apache.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

cloud.google.com/bigquery/docs

apacheignite.readme.io/docs

Developer

Alibaba

Google

Apache Software Foundation

Teradata

Initial release

2016

2010

2015

2005

Current release

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache 2.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++, Java, .Net

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

R packages

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes (replicated cache)

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

Since BigQuery is designed for querying data

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Security Hooks for custom implementations

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.