DBMS > Amazon Redshift vs. FoundationDB vs. GeoSpock vs. Manticore Search

System Properties Comparison Amazon Redshift vs. FoundationDB vs. GeoSpock vs. Manticore Search

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

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

geospock.com

manticoresearch.com

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

manual.manticoresearch.com

Developer

Amazon (based on PostgreSQL)

FoundationDB

GeoSpock

Manticore Software

Initial release

2012

2013

2017

Current release

6.2.28, November 2020

2.0, September 2019

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL version 2

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

C++

Server operating systems

hosted

Linux
OS X
Windows

hosted

FreeBSD
Linux
macOS
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

Fixed schema

Typing

predefined data types such as float or date

yes

some layers support typing

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

restricted

temporal, categorical

yes

full-text index on all search fields

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-like query language

APIs and other access methods

JDBC
ODBC

JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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.