DBMS > Atos Standard Common Repository vs. Axibase vs. LevelDB vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Axibase vs. LevelDB vs. Snowflake

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store

Relational DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

axibase.com/docs/atsd/finance

github.com/google/leveldb

www.snowflake.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Axibase Corporation

Google

Snowflake Computing Inc.

Initial release

2016

2013

2011

2014

Current release

1703

15585

1.23, February 2021

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

BSD

commercial

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

Illumos
Linux
OS X
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

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

Typing

predefined data types such as float or date

optional

yes

short, integer, long, float, double, decimal, string

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

SQL-like query language

yes

APIs and other access methods

LDAP

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Java
PHP
Python
R
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

with automatic compression on writes

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

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.