DBMS > Blazegraph vs. IRONdb vs. SiteWhere vs. Snowflake

System Properties Comparison Blazegraph vs. IRONdb vs. SiteWhere vs. Snowflake

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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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 Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

M2M integration platform for persisting/querying time series data

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

Primary database model

Graph DBMS
RDF store

Time Series DBMS

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	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

blazegraph.com

www.circonus.com/solutions/time-series-database/

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

wiki.blazegraph.com

docs.circonus.com/irondb/category/getting-started

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Blazegraph

Circonus LLC.

SiteWhere

Snowflake Computing Inc.

Initial release

2006

2017

2010

2014

Current release

2.1.5, March 2019

V0.10.20, January 2018

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

Open Source

Common Public Attribution License Version 1.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 and C++

Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Windows

hosted

Data scheme

schema-free

predefined scheme

yes

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

Typing

predefined data types such as float or date

yes

RDF literal types

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

HTTP API

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

yes, in Lua

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

selectable replication factor

based on HBase

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

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.

User concepts

Access control

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

Users with fine-grained authorization concept

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.