DBMS > HugeGraph vs. SQL.JS vs. SQLite vs. TerminusDB vs. TigerGraph

System Properties Comparison HugeGraph vs. SQL.JS vs. SQLite vs. TerminusDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Graph DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

github.com/hugegraph
hugegraph.apache.org

Technical documentation

hugegraph.apache.org/docs

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

docs.tigergraph.com

Developer

Baidu

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2018

2012

2000

2018

2017

Current release

0.9

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

GPL V3

commercial

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

JavaScript

Prolog, Rust

C++

Server operating systems

Linux
macOS
Unix

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

server-less

Linux

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

also supports composite index and range index

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

SQL-like query language (GSQL)

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Groovy
Java
Python

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

JavaScript
Python

C++
Java

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Foreign keys

Referential integrity

yes

edges in graph

yes

Relationships in graphs

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

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

in-memory journaling

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

Users, roles and permissions

Role-based access control

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.