DBMS > Blazegraph vs. Infobright vs. Qdrant vs. SAP HANA

System Properties Comparison Blazegraph vs. Infobright vs. Qdrant vs. SAP HANA

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A high-performance vector database with neural network or semantic-based matching

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

blazegraph.com

ignitetech.com/softwarelibrary/infobrightdb

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/hana.html

Technical documentation

wiki.blazegraph.com

qdrant.tech/documentation

help.sap.com/hana

Developer

Blazegraph

Ignite Technologies Inc.; formerly InfoBright Inc.

Qdrant

SAP

Initial release

2006

2005

2021

2010

Current release

2.1.5, March 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Rust

Server operating systems

Linux
OS X
Windows

Linux
Windows

Docker
Linux
macOS
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

yes

Numbers, Strings, Geo, Boolean

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

Knowledge Grid Technology used instead

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SPARQL is used as query language

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Collection-level replication

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

Eventual Consistency, tunable consistency

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.

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Key-based authentication

yes

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.