DBMS > HugeGraph vs. PostGIS vs. Rockset vs. Sphinx vs. SQLite

System Properties Comparison HugeGraph vs. PostGIS vs. Rockset vs. Sphinx vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

Spatial extension of PostgreSQL

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

Relational DBMS
Search engine

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

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/hugegraph
hugegraph.apache.org

Technical documentation

hugegraph.apache.org/docs

postgis.net/documentation

docs.rockset.com

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Baidu

Rockset

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2018

2005

2019

2001

2000

Current release

0.9

3.4.2, February 2024

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL v2.0

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

Linux
macOS
Unix

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

also supports composite index and range index

yes

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

HTTP REST

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Groovy
Java
Python

Go
Java
JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

yes

based on PostgreSQL

Automatic sharding

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

yes

based on PostgreSQL

yes

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

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

The original contents of fields are not stored in the Sphinx index.

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

yes

based on PostgreSQL

Access rights for users and organizations can be defined via Rockset console

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.