DBMS > Amazon Redshift vs. Datomic vs. Ehcache vs. Firebird vs. NSDb

System Properties Comparison Amazon Redshift vs. Datomic vs. Ehcache vs. Firebird vs. NSDb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted Java cache with tiered storage options

Firebird is an open source RDBMS forked from Borland's InterBase

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

www.ehcache.org/documentation

www.firebirdsql.org/en/reference-manuals

nsdb.io/Architecture

Developer

Amazon (based on PostgreSQL)

Cognitect

Terracotta Inc, owned by Software AG

Firebird Foundation

Initial release

2012

2009

2000

As fork of Borland's InterBase

2017

Current release

1.0.6735, June 2023

3.10.0, March 2022

5.0.0, January 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

Open Source

Initial Developer's Public License

Open Source

Apache Version 2.0

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, Clojure

Java

C and C++

Java, Scala

Server operating systems

hosted

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JCache

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

PSQL

Triggers

By using transaction functions

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

by using Terracotta Server

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

using a tiered cache-storage approach

yes

Using Apache Lucene

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.