DBMS > Atos Standard Common Repository vs. etcd vs. Oracle Coherence vs. Snowflake vs. Tkrzw

System Properties Comparison Atos Standard Common Repository vs. etcd vs. Oracle Coherence vs. Snowflake vs. Tkrzw

Editorial information provided by DB-Engines

Name

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

Description

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

A distributed reliable key-value store

Oracles in-memory data grid solution

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Key-value store

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

etcd.io
github.com/etcd-io/etcd

www.oracle.com/java/coherence

www.snowflake.com

dbmx.net/tkrzw

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.oracle.com/en/middleware/standalone/coherence

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Oracle

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2016

2007

2014

2020

Current release

1703

3.4, August 2019

14.1, August 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0

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

Linux

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

hosted

Linux
macOS

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

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

SQL

Support of SQL

yes

APIs and other access methods

LDAP

gRPC
JSON over HTTP

JCache
JPA
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C++
Java

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

yes, watching key changes

yes

Live Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes, with selectable consistency level

yes

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

Immediate Consistency

Eventual Consistency
Immediate 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

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

LDAP bind authentication

authentification to access the cache via certificates or http basic authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

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.