DBMS > Amazon Redshift vs. FatDB vs. SingleStore vs. XTDB

System Properties Comparison Amazon Redshift vs. FatDB vs. SingleStore vs. XTDB

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.

Description

Large scale data warehouse service for use with business intelligence tools

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

aws.amazon.com/redshift

www.singlestore.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.singlestore.com

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

FatCloud

SingleStore Inc.

Juxt Ltd.

Initial release

2012

2013

2019

Current release

8.5, January 2024

1.19, September 2021

License

Commercial or Open Source

commercial

free developer edition available

Open Source

MIT License

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++, Go

Clojure

Server operating systems

hosted

Windows

Linux

64 bit version required

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Via inetgration in SQL Server

yes

but no triggers and foreign keys

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

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

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

Bash
C
C#
Java
JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

yes

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

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

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Fine grained access control via users, groups and roles

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.