DBMS > Amazon Redshift vs. FoundationDB vs. GeoSpock vs. QuestDB

System Properties Comparison Amazon Redshift vs. FoundationDB vs. GeoSpock vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in 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

Ordered key-value store. Core features are complimented by layers.

Spatial and temporal data processing engine for extreme data scale

A high performance open source SQL database for time series data

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.97
Rank	#191	Overall
	#32	Document stores
	#28	Key-value stores
	#87	Relational DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

geospock.com

questdb.io

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

questdb.io/docs

Developer

Amazon (based on PostgreSQL)

FoundationDB

GeoSpock

QuestDB Technology Inc

Initial release

2012

2013

2014

Current release

6.2.28, November 2020

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache 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

C++

Java, Javascript

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux
macOS
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes

some layers support typing

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

temporal, categorical

SQL

Support of SQL

yes

does not fully support an SQL-standard

supported in specific SQL layer only

ANSI SQL for query only (using Presto)

SQL with time-series extensions

APIs and other access methods

JDBC
ODBC

JDBC

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

in SQL-layer only

Transaction concepts

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

ACID

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

The story of our SAMPLE BY enhancements
7 August 2024

A cloud engineer's first QuestDB Pull Request
5 August 2024

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.