DBMS > Amazon Redshift vs. FatDB vs. InterSystems Caché vs. MarkLogic

System Properties Comparison Amazon Redshift vs. FatDB vs. InterSystems Caché vs. MarkLogic

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.

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines 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.

A multi-model DBMS and application server

Operational and transactional Enterprise NoSQL database

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store
Object oriented DBMS
Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Website

aws.amazon.com/redshift

www.intersystems.com/products/cache

www.marklogic.com

Technical documentation

docs.aws.amazon.com/redshift

docs.intersystems.com

docs.marklogic.com

Developer

Amazon (based on PostgreSQL)

FatCloud

InterSystems

MarkLogic Corp.

Initial release

2012

1997

2001

Current release

2018.1.4, May 2020

11.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is 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

C++

Server operating systems

hosted

Windows

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

depending on used data model

schema-free

Schema can be enforced

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

yes

SQL92

APIs and other access methods

JDBC
ODBC

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

.NET Client API
JDBC
ODBC
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

yes

via XQuery or JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

Access rights for users, groups and roles

Role-based access control at the document and subdocument levels

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.