DBMS > Amazon Redshift vs. BigObject vs. CrateDB vs. Ehcache

System Properties Comparison Amazon Redshift vs. BigObject vs. CrateDB vs. Ehcache

Please select another system to include it in the comparison.

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

Distributed Database based on Lucene

A widely adopted Java cache with tiered storage options

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Website

aws.amazon.com/redshift

bigobject.io

cratedb.com

www.ehcache.org

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

cratedb.com/docs

www.ehcache.org/documentation

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Crate

Terracotta Inc, owned by Software AG

Initial release

2012

2015

2013

2009

Current release

3.10.0, March 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

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

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 Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

All OS with a Java VM

Data scheme

yes

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

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

SQL-like DML and DDL statements

yes, but no triggers and constraints, and PostgreSQL compatibility

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

JCache

Supported programming languages

All languages supporting JDBC/ODBC

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Java

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

user defined functions (Javascript)

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

by using Terracotta Server

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Configurable replication on table/partition-level

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

Eventual Consistency
Read-after-write consistency on record level

Tunable Consistency (Strong, Eventual, Weak)

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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 a tiered cache-storage approach

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

rights management via user accounts

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.