DBMS > Amazon Redshift vs. Databricks vs. EsgynDB vs. Google Cloud Bigtable vs. RRDtool

System Properties Comparison Amazon Redshift vs. Databricks vs. EsgynDB vs. Google Cloud Bigtable vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store
Wide column 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	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/redshift

www.databricks.com

www.esgyn.cn

cloud.google.com/bigtable

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

cloud.google.com/bigtable/docs

oss.oetiker.ch/rrdtool/doc

Developer

Amazon (based on PostgreSQL)

Databricks

Esgyn

Google

Tobias Oetiker

Initial release

2012

2013

2015

1999

Current release

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

Linux

hosted

HP-UX
Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

in-process shared library
Pipes

Supported programming languages

All languages supporting JDBC/ODBC

Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

Java Stored Procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

none

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

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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 (IAM)

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.