DBMS > Atos Standard Common Repository vs. KeyDB vs. Snowflake vs. ToroDB

System Properties Comparison Atos Standard Common Repository vs. KeyDB vs. Snowflake vs. ToroDB

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.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Cloud-based data warehousing service for structured and semi-structured data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Document store

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

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

github.com/Snapchat/KeyDB
keydb.dev

www.snowflake.com

github.com/torodb/server

Technical documentation

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

8Kdata

Initial release

2016

2019

2014

2016

Current release

1703

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

Open Source

AGPL-V3

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++

Java

Server operating systems

Linux

hosted

All OS with a Java 7 VM

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

optional

partial

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

yes

string, integer, double, boolean, date, object_id

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

yes

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protoco

CLI Client
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

Optimistic locking, atomic execution of commands blocks and scripts

ACID

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

User concepts

Access control

LDAP bind authentication

simple password-based access control and ACL

Users with fine-grained authorization concept, user roles and pluggable 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.