DBMS > HugeGraph vs. MySQL vs. Oracle vs. Oracle Berkeley DB vs. XTDB

System Properties Comparison HugeGraph vs. MySQL vs. Oracle vs. Oracle Berkeley DB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

Widely used open source RDBMS

Widely used RDBMS

Widely used in-process key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/hugegraph
hugegraph.apache.org

www.mysql.com

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

hugegraph.apache.org/docs

dev.mysql.com/doc

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

www.xtdb.com/docs

Developer

Baidu

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Juxt Ltd.

Initial release

2018

1995

1980

1994

2019

Current release

0.9

8.4.0, April 2024

23c, September 2023

18.1.40, May 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

Open Source

commercial license available

Open Source

MIT License

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

Java

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Clojure

Server operating systems

Linux
macOS
Unix

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

only with the Berkeley DB XML edition

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

limited SQL, making use of Apache Calcite

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST
JDBC

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Clojure
Java

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

yes

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Multi-source replication
Source-replica replication

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Users, roles and permissions

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.