DBMS > Amazon Redshift vs. atoti vs. Datomic vs. Faircom EDGE

System Properties Comparison Amazon Redshift vs. atoti vs. Datomic vs. Faircom EDGE

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Primary database model

Relational DBMS

Object oriented DBMS

Relational DBMS

Key-value store
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.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Website

aws.amazon.com/redshift

atoti.io

www.datomic.com

www.faircom.com/products/faircom-edge

Technical documentation

docs.aws.amazon.com/redshift

docs.atoti.io

docs.datomic.com

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

Developer

Amazon (based on PostgreSQL)

ActiveViam

Cognitect

FairCom Corporation

Initial release

2012

1979

Current release

1.0.6735, June 2023

V3, October 2020

License

Commercial or Open Source

commercial

free versions available

commercial

limited edition free

commercial

Restricted, free version 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

Java

Java, Clojure

ANSI C, C++

Server operating systems

hosted

All OS with a Java VM

Android
Linux

ARM, x86
Raspbian
Windows

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

Multidimensional Expressions (MDX)

yes

ANSI SQL queries

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

Server-side scripts

Stored procedures

user defined functions

in Python

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

Sharding, horizontal partitioning

none

But extensive use of caching in the application peers

File partitioning

Customizable business rules for partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

Synchronous and asynchronous realtime replication based on transaction logs

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

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

across SQL and NoSQL

Durability

Support for making data persistent

yes

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

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 user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.