DBMS > Blazegraph vs. HugeGraph vs. Microsoft SQL Server vs. SiteWhere vs. Spark SQL

System Properties Comparison Blazegraph vs. HugeGraph vs. Microsoft SQL Server vs. SiteWhere vs. Spark SQL

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 fast-speed and highly-scalable Graph DBMS

Microsofts flagship relational DBMS

M2M integration platform for persisting/querying time series data

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Secondary database models

Document store
Graph DBMS
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.13
Rank	#336	Overall
	#32	Graph DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

blazegraph.com

github.com/hugegraph
hugegraph.apache.org

www.microsoft.com/en-us/sql-server

github.com/sitewhere/sitewhere

spark.apache.org/sql

Technical documentation

wiki.blazegraph.com

hugegraph.apache.org/docs

learn.microsoft.com/en-US/sql/sql-server

sitewhere1.sitewhere.io/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Blazegraph

Baidu

Microsoft

SiteWhere

Apache Software Foundation

Initial release

2006

2018

1989

2010

2014

Current release

2.1.5, March 2019

0.9

SQL Server 2022, November 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Java

Scala

Server operating systems

Linux
OS X
Windows

Linux
macOS
Unix

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

yes

Typing

predefined data types such as float or date

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

also supports composite index and range index

yes

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-like DML and DDL statements

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST

JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Groovy
Java
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

asynchronous Gremlin script jobs

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

based on HBase

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

edges in graph

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.

yes

User concepts

Access control

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

Users, roles and permissions

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.