DBMS > Amazon Neptune vs. Blazegraph vs. GeoMesa vs. LeanXcale

System Properties Comparison Amazon Neptune vs. Blazegraph vs. GeoMesa vs. LeanXcale

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

Fast, reliable graph database built for the cloud

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Primary database model

Graph DBMS
RDF store

Spatial DBMS

Key-value store
Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.81
Rank	#213	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Website

aws.amazon.com/neptune

blazegraph.com

www.geomesa.org

www.leanxcale.com

Technical documentation

aws.amazon.com/neptune/developer-resources

wiki.blazegraph.com

www.geomesa.org/documentation/stable/user/index.html

Developer

Amazon

Blazegraph

CCRi and others

LeanXcale

Initial release

2017

2006

2014

2015

Current release

2.1.5, March 2019

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Apache License 2.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

Scala

Server operating systems

hosted

Linux
OS X
Windows

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

SQL

Support of SQL

SPARQL is used as query language

yes

through Apache Derby

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C
Java
Scala

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

with encyption-at-rest

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Exploring new features of Apache TinkerPop 3.7.x in Amazon Neptune | Amazon Web Services
7 June 2024, AWS Blog

Building NHM London's Planetary Knowledge Base with Amazon Neptune and the Registry of Open Data on AWS ...
5 June 2024, AWS Blog

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune | Amazon Web Services
3 June 2024, AWS Blog

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

provided by Google News

Back to the future: Does graph database success hang on query language?
5 March 2018, ZDNet

Video: Blazegraph Accelerates Graph Computing with GPUs - High-Performance Computing News Analysis
20 December 2015, insideHPC

Harnessing GPUs Delivers a Big Speedup for Graph Analytics
15 December 2015, Datanami

This AI Paper Introduces A Comprehensive RDF Dataset With Over 26 Billion Triples Covering Scholarly Data Across All Scientific Disciplines
19 August 2023, MarkTechPost

Representation Learning on RDF* and LPG Knowledge Graphs
24 September 2020, Towards Data Science

provided by Google News

Share this page