DBMS > Firebase Realtime Database vs. Memcached vs. Snowflake vs. SQream DB vs. Teradata Aster

System Properties Comparison Firebase Realtime Database vs. Memcached vs. Snowflake vs. SQream DB 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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

In-memory key-value store, originally intended for caching

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

a GPU-based, columnar RDBMS for big data analytics workloads

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Key-value store

Relational DBMS

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

Score	13.43
Rank	#39	Overall
	#6	Document stores

Score	16.99
Rank	#32	Overall
	#4	Key-value stores

Score	142.50
Rank	#7	Overall
	#5	Relational DBMS

Score	0.63
Rank	#229	Overall
	#107	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.memcached.org

www.snowflake.com

sqream.com

Technical documentation

firebase.google.com/docs/database

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Google

acquired by Google 2014

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

SQream Technologies

Teradata

Initial release

2012

2003

2014

2017

2005

Current release

1.6.29, June 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

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++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

Data scheme

schema-free

yes

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

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

yes, ANSI Standard SQL Types

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

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

user defined functions in Python

R packages

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

none

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

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

User concepts

Access control

yes, based on authentication and database rules

yes

using SASL (Simple Authentication and Security Layer) protocol

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

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.