DBMS > Blazegraph vs. Hypertable vs. Microsoft SQL Server vs. Vitess

System Properties Comparison Blazegraph vs. Hypertable vs. Microsoft SQL Server vs. Vitess

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.

Hypertable has stopped its further development with March 2016 and is removed 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.

An open source BigTable implementation based on distributed file systems such as Hadoop

Microsofts flagship relational DBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Graph DBMS
RDF store

Wide column store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

blazegraph.com

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

vitess.io

Technical documentation

wiki.blazegraph.com

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

vitess.io/docs

Developer

Blazegraph

Hypertable Inc.

Microsoft

The Linux Foundation, PlanetScale

Initial release

2006

2009

1989

2013

Current release

2.1.5, March 2019

0.9.8.11, March 2016

SQL Server 2022, November 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

GNU version 3. Commercial license available

commercial

restricted free version is available

Open Source

Apache Version 2.0, commercial licenses available

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++

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

C++ API
Thrift

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C++
Java
Perl
PHP
Python
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor on file system level

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.