DBMS > Amazon Redshift vs. Cachelot.io vs. Datomic vs. Faircom DB vs. SpatiaLite

System Properties Comparison Amazon Redshift vs. Cachelot.io vs. Datomic vs. Faircom DB vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

In-memory caching system

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Spatial extension of SQLite

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key-value store
Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

aws.amazon.com/redshift

cachelot.io

www.datomic.com

www.faircom.com/products/faircom-db

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Amazon (based on PostgreSQL)

Cognitect

FairCom Corporation

Alessandro Furieri

Initial release

2012

2015

2012

1979

2008

Current release

1.0.6735, June 2023

V12, November 2020

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Simplified BSD License

commercial

limited edition free

commercial

Restricted, free version available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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, Clojure

ANSI C, C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

server-less

Data scheme

yes

schema-free

yes

schema free, schema optional, schema required, partial schema,

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

Memcached protocol

RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Clojure
Java

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

.Net, JavaScript, C/C++

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Fine grained access rights according to SQL-standard with additional protections for files

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.