DBMS > Blazegraph vs. GeoSpock vs. SAP HANA

System Properties Comparison Blazegraph vs. GeoSpock 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.

GeoSpock seems to be discontinued. Therefore it will be 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.

Spatial and temporal data processing engine for extreme data scale

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Time Series DBMS

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.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

blazegraph.com

geospock.com

www.sap.com/products/hana.html

Technical documentation

wiki.blazegraph.com

help.sap.com/hana

Developer

Blazegraph

GeoSpock

SAP

Initial release

2006

2010

Current release

2.1.5, March 2019

2.0, September 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java, Javascript

Server operating systems

Linux
OS X
Windows

hosted

Appliance or cloud-service

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

SPARQL is used as query language

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC

JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

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)

Access rights for users can be defined per table

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.