DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. Datomic vs. Percona Server for MongoDB

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. Datomic vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.datomic.com

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

docs.percona.com/percona-distribution-for-mongodb

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Cognitect

Percona

Initial release

2012

2016

2012

2015

Current release

1703

1.0.6735, June 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

limited edition free

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

Java

Java, Clojure

C++

Server operating systems

hosted

Linux

All OS with a Java VM

Linux

Data scheme

yes

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

APIs and other access methods

JDBC
ODBC

LDAP

RESTful HTTP API

proprietary protocol using JSON

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Clojure
Java

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

JavaScript

Triggers

yes

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual 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

Atomic execution of specific operations

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

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

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

Access rights for users 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.