DBMS > Blazegraph vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Valentina Server

System Properties Comparison Blazegraph vs. Graph Engine vs. Microsoft Azure Cosmos DB vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Globally distributed, horizontally scalable, multi-model database service

Object-relational database and reports server

Primary database model

Graph DBMS
RDF store

Graph DBMS
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

blazegraph.com

www.graphengine.io

azure.microsoft.com/services/cosmos-db

www.valentina-db.net

Technical documentation

wiki.blazegraph.com

www.graphengine.io/docs/manual

learn.microsoft.com/azure/cosmos-db

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Blazegraph

Microsoft

Paradigma Software

Initial release

2006

2010

2014

1999

Current release

2.1.5, March 2019

5.7.5

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

MIT License

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

.NET and C

Server operating systems

Linux
OS X
Windows

.NET

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SPARQL is used as query language

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.