DBMS > Atos Standard Common Repository vs. Badger vs. Dolt vs. EXASOL vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Badger vs. Dolt vs. EXASOL vs. Snowflake

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A MySQL compatible DBMS with Git-like versioning of data and schema

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

github.com/dgraph-io/badger

github.com/dolthub/dolt
www.dolthub.com

www.exasol.com

www.snowflake.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.dolthub.com

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

DGraph Labs

DoltHub Inc

Exasol

Snowflake Computing Inc.

Initial release

2016

2017

2018

2000

2014

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

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

CLI Client
HTTP REST

.Net
JDBC
ODBC
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Lua
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

none

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

User concepts

Access control

LDAP bind authentication

Only one user is configurable, and must be specified in the config file at startup

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

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.