DBMS > Atos Standard Common Repository vs. Galaxybase vs. MarkLogic vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Galaxybase vs. MarkLogic 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, ACID-compliant native distributed parallel graph platform

Operational and transactional Enterprise NoSQL database

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

Primary database model

Document store
Key-value store

Graph DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

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

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

galaxybase.com

www.progress.com/marklogic

www.snowflake.com

Technical documentation

www.progress.com/marklogic/documentation

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

MarkLogic Corp.

Snowflake Computing Inc.

Initial release

2016

2017

2001

2014

Current release

1703

Nov 20, November 2021

11.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

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 and Java

C++

Server operating systems

Linux

Linux
OS X
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

Strong typed schema

schema-free

Schema can be enforced

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

SQL92

yes

APIs and other access methods

LDAP

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Java
Python

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined procedures and functions

yes

via XQuery or JavaScript

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

Relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

User concepts

Access control

LDAP bind authentication

Role-based access control

Role-based access control at the document and subdocument levels

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.