DBMS > AgensGraph vs. Faircom DB vs. HugeGraph vs. MySQL

System Properties Comparison AgensGraph vs. Faircom DB vs. HugeGraph vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

A fast-speed and highly-scalable Graph DBMS

Widely used open source RDBMS

Primary database model

Graph DBMS
Relational DBMS

Key-value store
Relational DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

bitnine.net/agensgraph

www.faircom.com/products/faircom-db

github.com/hugegraph
hugegraph.apache.org

www.mysql.com

Technical documentation

bitnine.net/documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

hugegraph.apache.org/docs

dev.mysql.com/doc

Developer

Bitnine Global Inc.

FairCom Corporation

Baidu

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

1979

2018

1995

Current release

2.1, December 2018

V12, November 2020

0.9

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Restricted, free version available

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

ANSI C, C++

Java

C and C++

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
macOS
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

depending on used data model

schema free, schema optional, schema required, partial schema,

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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.

yes

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

Cypher Query Language
JDBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
Java
JavaScript
Python

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Groovy
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

asynchronous Gremlin script jobs

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

fine grained access rights according to SQL-standard

Fine grained access rights according to SQL-standard with additional protections for files

Users, roles and permissions

Users with fine-grained authorization concept

no user groups or roles

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.