DBMS > Hazelcast vs. HugeGraph vs. SQL.JS vs. SQLite

System Properties Comparison Hazelcast vs. HugeGraph vs. SQL.JS vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

A fast-speed and highly-scalable Graph DBMS

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Graph DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	0.53
Rank	#252	Overall
	#116	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

github.com/hugegraph
hugegraph.apache.org

sql.js.org

www.sqlite.org

Technical documentation

hazelcast.org/imdg/docs

hugegraph.apache.org/docs

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Hazelcast

Baidu

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2008

2018

2012

2000

Current release

5.3.6, November 2023

0.9

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2.0

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

JavaScript

Server operating systems

All OS with a Java VM

Linux
macOS
Unix

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

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

the object must implement a serialization strategy

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
TinkerPop Gremlin

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

asynchronous Gremlin script jobs

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

none

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

except by serializing a db to a file

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

Role-based access control

Users, roles and permissions

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.