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

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. KeyDB 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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

aws.amazon.com/redshift

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

github.com/Snapchat/KeyDB
keydb.dev

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

Technical documentation

docs.aws.amazon.com/redshift

docs.keydb.dev

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

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

EQ Alpha Technology Ltd.

Percona

Initial release

2012

2016

2019

2015

Current release

1703

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

BSD-3

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

C++

Server operating systems

hosted

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

LDAP

Proprietary protocol

RESP - REdis Serialization Protoco

proprietary protocol using JSON

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Lua

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

yes

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

simple password-based access control and ACL

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.