DBMS > Amazon Redshift vs. Databend vs. Firebase Realtime Database vs. OrientDB vs. Yanza

System Properties Comparison Amazon Redshift vs. Databend vs. Firebase Realtime Database vs. OrientDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Multi-model DBMS (Document, Graph, Key/Value)

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Website

aws.amazon.com/redshift

github.com/datafuselabs/databend
www.databend.com

firebase.google.com/products/realtime-database

orientdb.org

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

docs.databend.com

firebase.google.com/docs/database

www.orientdb.com/docs/last/index.html

Developer

Amazon (based on PostgreSQL)

Databend Labs

Google

acquired by Google 2014

OrientDB LTD; CallidusCloud; SAP

Yanza

Initial release

2012

2021

2012

2010

2015

Current release

1.0.59, April 2023

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Rust

Java

Server operating systems

hosted

hosted
Linux
macOS

hosted

All OS with a Java JDK (>= JDK 6)

Windows

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

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

SQL-like query language, no joins

APIs and other access methods

JDBC
ODBC

CLI Client
JDBC
RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python
Rust

Java
JavaScript
Objective-C

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

Java, Javascript

Triggers

Callbacks are triggered when data changes

Hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

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

relationship in graphs

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

Users with fine-grained authorization concept, user roles

yes, based on authentication and database rules

Access rights for users and roles; record level security configurable

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.