DBMS > Amazon Redshift vs. Firebase Realtime Database vs. Sadas Engine vs. VoltDB

System Properties Comparison Amazon Redshift vs. Firebase Realtime Database vs. Sadas Engine vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

firebase.google.com/products/realtime-database

www.sadasengine.com

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

SADAS s.r.l.

VoltDB Inc.

Initial release

2012

2006

2010

Current release

8.0

11.3, April 2022

License

Commercial or Open Source

commercial

free trial version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

hosted

AIX
Linux
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

.Net
C
C#
C++
Groovy
Java
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

Java

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights for users, groups and roles according to SQL-standard

Users and roles with access to stored procedures

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.