DBMS > Blazegraph vs. Dragonfly vs. Graphite vs. Microsoft Azure Cosmos DB

System Properties Comparison Blazegraph vs. Dragonfly vs. Graphite vs. Microsoft Azure Cosmos DB

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 drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Graph DBMS
RDF store

Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial 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	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

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

Website

blazegraph.com

github.com/dragonflydb/dragonfly
www.dragonflydb.io

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

Technical documentation

wiki.blazegraph.com

www.dragonflydb.io/docs

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

Developer

Blazegraph

DragonflyDB team and community contributors

Chris Davis

Microsoft

Initial release

2006

2023

2006

2014

Current release

2.1.5, March 2019

1.0, March 2023

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

BSL 1.1

Open Source

Apache 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

C++

Python

Server operating systems

Linux
OS X
Windows

Linux

Linux
Unix

hosted

Data scheme

schema-free

scheme-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

strings, hashes, lists, sets, sorted sets, bit arrays

Numeric data only

yes

JSON types

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

SQL

Support of SQL

SPARQL is used as query language

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Sockets

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

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

Lua

JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

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

Eventual Consistency

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

locking

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

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

Password-based authentication

Access rights can be defined down to the item level

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.