DBMS > Blazegraph vs. GridGain vs. IBM Db2 vs. SQLite

System Properties Comparison Blazegraph vs. GridGain vs. IBM Db2 vs. SQLite

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.

GridGain is an in-memory computing platform, built on Apache Ignite

Common in IBM host environments, 2 different versions for host and Windows/Linux

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
RDF store

Key-value store
Relational DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

blazegraph.com

www.gridgain.com

www.ibm.com/products/db2

www.sqlite.org

Technical documentation

wiki.blazegraph.com

www.gridgain.com/docs/index.html

www.ibm.com/docs/en/db2

www.sqlite.org/docs.html

Developer

Blazegraph

GridGain Systems, Inc.

IBM

Dwayne Richard Hipp

Initial release

2006

2007

1983

host version

2000

Current release

2.1.5, March 2019

GridGain 8.5.1

12.1, October 2016

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

free version is available

Open Source

Public Domain

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

Java, C++, .Net

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

RDF literal types

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SPARQL is used as query language

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

yes

with separate tools (MQ, InfoSphere)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

via file-system locks

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)

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.