DBMS > Amazon Redshift vs. Ehcache vs. Firebolt vs. RavenDB vs. SWC-DB

System Properties Comparison Amazon Redshift vs. Ehcache vs. Firebolt vs. RavenDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

aws.amazon.com/redshift

www.ehcache.org

www.firebolt.io

ravendb.net

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

docs.firebolt.io

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Firebolt Analytics Inc.

Hibernating Rhinos

Alex Kashirin

Initial release

2012

2009

2020

2010

2020

Current release

3.10.0, March 2022

5.4, July 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

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

Server operating systems

hosted

All OS with a Java VM

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

schema-free

yes

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

SQL-like query language

APIs and other access methods

JDBC
ODBC

JCache

.Net
ODBC
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Proprietary protocol
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

Java

Go
JavaScript (Node.js)
Python

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

C++

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Authorization levels configured per client per database

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.