DBMS > Atos Standard Common Repository vs. KeyDB vs. Sadas Engine vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. KeyDB vs. Sadas Engine vs. Yanza

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.

Yanza 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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Time Series DBMS

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

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

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

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

github.com/Snapchat/KeyDB
keydb.dev

www.sadasengine.com

yanza.com

Technical documentation

docs.keydb.dev

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Atos Convergence Creators

EQ Alpha Technology Ltd.

SADAS s.r.l.

Yanza

Initial release

2016

2019

2006

2015

Current release

1703

8.0

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

free trial version available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Linux

AIX
Linux
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

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

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC
Proprietary protocol

HTTP API

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

Lua

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

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

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

managed by 'Learn by Usage'

User concepts

Access control

LDAP bind authentication

simple password-based access control and ACL

Access rights for users, groups and roles according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, microsoft.com

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

provided by Google News

Share this page