DBMS > Amazon Redshift vs. Derby vs. FatDB vs. GeoSpock

System Properties Comparison Amazon Redshift vs. Derby vs. FatDB vs. GeoSpock

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial and temporal data processing engine for extreme data scale

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

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.60
Rank	#70	Overall
	#38	Relational DBMS

Website

aws.amazon.com/redshift

db.apache.org/derby

geospock.com

Technical documentation

docs.aws.amazon.com/redshift

db.apache.org/derby/manuals/index.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

FatCloud

GeoSpock

Initial release

2012

1997

2012

Current release

10.17.1.0, November 2023

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

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

Java, Javascript

Server operating systems

hosted

All OS with a Java VM

Windows

hosted

Data scheme

yes

schema-free

yes

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.

yes

Secondary indexes

restricted

yes

temporal, categorical

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

APIs and other access methods

JDBC
ODBC

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC

Supported programming languages

All languages supporting JDBC/ODBC

Java

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

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

Can implement custom security layer via applications

Access rights for users can be defined per table

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.