DBMS > Amazon Redshift vs. BoltDB vs. Google Cloud Firestore vs. Heroic vs. Teradata Aster

System Properties Comparison Amazon Redshift vs. BoltDB vs. Google Cloud Firestore vs. Heroic vs. Teradata Aster

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

Large scale data warehouse service for use with business intelligence tools

An embedded key-value store for Go.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Platform for big data analytics on multistructured data sources and types

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/boltdb/bolt

firebase.google.com/products/firestore

github.com/spotify/heroic

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/firestore

spotify.github.io/heroic

Developer

Amazon (based on PostgreSQL)

Google

Spotify

Teradata

Initial release

2012

2013

2017

2014

2005

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Java

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

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

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes, Firebase Rules & Cloud Functions

R packages

Triggers

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

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

Using Cloud Dataflow

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

yes

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.