DBMS > HugeGraph vs. Infobright vs. Qdrant vs. SQL.JS vs. SQLite

System Properties Comparison HugeGraph vs. Infobright vs. Qdrant vs. SQL.JS vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A high-performance vector database with neural network or semantic-based matching

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	0.53
Rank	#252	Overall
	#116	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/hugegraph
hugegraph.apache.org

ignitetech.com/softwarelibrary/infobrightdb

github.com/qdrant/qdrant
qdrant.tech

sql.js.org

www.sqlite.org

Technical documentation

hugegraph.apache.org/docs

qdrant.tech/documentation

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Baidu

Ignite Technologies Inc.; formerly InfoBright Inc.

Qdrant

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2018

2005

2021

2012

2000

Current release

0.9

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Rust

JavaScript

Server operating systems

Linux
macOS
Unix

Linux
Windows

Docker
Linux
macOS
Windows

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

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

also supports composite index and range index

Knowledge Grid Technology used instead

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Groovy
Java
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

asynchronous Gremlin script jobs

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Source-replica replication

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

none

Foreign keys

Referential integrity

yes

edges in graph

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

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

Users, roles and permissions

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Key-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.