DBMS > Atos Standard Common Repository vs. Blazegraph vs. Datomic vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Blazegraph vs. Datomic 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.

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

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

Score	0.81
Rank	#213	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

blazegraph.com

www.datomic.com

www.snowflake.com

Technical documentation

wiki.blazegraph.com

docs.datomic.com

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Blazegraph

Cognitect

Snowflake Computing Inc.

Initial release

2016

2006

2012

2014

Current release

1703

2.1.5, March 2019

1.0.7075, December 2023

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

commercial

limited edition free

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

Java, Clojure

Server operating systems

Linux

Linux
OS X
Windows

All OS with a Java VM

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

RDF literal types

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

SPARQL is used as query language

yes

APIs and other access methods

LDAP

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Clojure
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

yes

By using transaction functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

But extensive use of caching in the application peers

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

LDAP bind authentication

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.