DBMS > Amazon Redshift vs. BaseX vs. Dgraph vs. EsgynDB vs. Firebase Realtime Database

System Properties Comparison Amazon Redshift vs. BaseX vs. Dgraph vs. EsgynDB vs. Firebase Realtime Database

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

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	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Website

aws.amazon.com/redshift

basex.org

dgraph.io

www.esgyn.cn

firebase.google.com/products/realtime-database

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

dgraph.io/docs

firebase.google.com/docs/database

Developer

Amazon (based on PostgreSQL)

BaseX GmbH

Dgraph Labs, Inc.

Esgyn

Google

acquired by Google 2014

Initial release

2012

2007

2016

2015

2012

Current release

10.7, August 2023

License

Commercial or Open Source

commercial

Open Source

BSD license

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

C++, Java

Server operating systems

hosted

Linux
OS X
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports 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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java Stored Procedures

limited functionality with using 'rules'

Triggers

yes

via events

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Synchronous replication via Raft

Multi-source replication between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

multiple readers, single writer

ACID

yes

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 on 4 levels

Planned for future releases

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

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.