DBMS > Atos Standard Common Repository vs. RDFox vs. Snowflake vs. Tkrzw

System Properties Comparison Atos Standard Common Repository vs. RDFox vs. Snowflake vs. Tkrzw

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

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

High performance knowledge graph and semantic reasoning engine

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

Graph DBMS
RDF store

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

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

www.oxfordsemantic.tech

www.snowflake.com

dbmx.net/tkrzw

Technical documentation

docs.oxfordsemantic.tech

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Oxford Semantic Technologies

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2016

2017

2014

2020

Current release

1703

6.0, Septermber 2022

0.9.3, August 2020

License

Commercial or Open Source

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

Linux
macOS
Windows

hosted

Linux
macOS

Data scheme

Schema and schema-less with LDAP views

yes

RDF schemas

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

RESTful HTTP API
SPARQL 1.1

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C
Java

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

replication via a shared file system

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 in stand-alone mode, Eventual Consistency in replicated setups

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Roles, resources, and access types

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.