DBMS > Blazegraph vs. Dragonfly vs. PouchDB vs. SQLite

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

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.74
Rank	#217	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.44
Rank	#255	Overall
	#38	Key-value stores

Score	2.18
Rank	#114	Overall
	#21	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

blazegraph.com

github.com/dragonflydb/dragonfly
www.dragonflydb.io

pouchdb.com

www.sqlite.org

Technical documentation

wiki.blazegraph.com

www.dragonflydb.io/docs

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Blazegraph

DragonflyDB team and community contributors

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2006

2023

2012

2000

Current release

2.1.5, March 2019

1.0, March 2023

7.1.1, June 2019

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

BSL 1.1

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

C++

JavaScript

Server operating systems

Linux
OS X
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

schema-free

scheme-free

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

RDF literal types

strings, hashes, lists, sets, sorted sets, bit arrays

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

JavaScript

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

Lua

View functions in JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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)

Password-based authentication

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.