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

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

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

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

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.datomic.com

www.ehcache.org/documentation

nsdb.io/Architecture

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Cognitect

Terracotta Inc, owned by Software AG

Initial release

2012

2015

2012

2009

2017

Current release

1.0.6735, June 2023

3.10.0, March 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

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

Java, Scala

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Linux
macOS

Data scheme

yes

schema-free

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

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

RESTful HTTP API

JCache

gRPC
HTTP REST
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java

Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

Transaction Functions

Triggers

By using transaction functions

yes

Cache Event Listeners

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

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

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

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.