DBMS > Google Cloud Bigtable vs. SAP Advantage Database Server vs. Snowflake vs. Teradata Aster vs. ToroDB

System Properties Comparison Google Cloud Bigtable vs. SAP Advantage Database Server vs. Snowflake vs. Teradata Aster vs. ToroDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Platform for big data analytics on multistructured data sources and types

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store
Wide column store

Relational DBMS

Document store

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cloud.google.com/bigtable

www.sap.com/products/advantage-database-server.html

www.snowflake.com

github.com/torodb/server

Technical documentation

cloud.google.com/bigtable/docs

docs.snowflake.net/manuals/index.html

Developer

Google

Sybase, SAP

Snowflake Computing Inc.

Teradata

8Kdata

Initial release

2015

1993

2014

2005

2016

License

Commercial or Open Source

commercial

Open Source

AGPL-V3

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

Server operating systems

hosted

Linux
Windows

hosted

Linux

All OS with a Java 7 VM

Data scheme

schema-free

yes

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

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

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

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

Delphi
Perl
PHP

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

R packages

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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.

caching of (temporary) tables can be configured

User concepts

Access control

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

Access rights for users and roles

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.