DBMS > Drizzle vs. HugeGraph vs. Oracle vs. Yanza

System Properties Comparison Drizzle vs. HugeGraph vs. Oracle vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A fast-speed and highly-scalable Graph DBMS

Widely used RDBMS

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

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.17
Rank	#335	Overall
	#31	Graph DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

github.com/hugegraph
hugegraph.apache.org

www.oracle.com/database

yanza.com

Technical documentation

hugegraph.apache.org/docs

docs.oracle.com/en/database

Developer

Drizzle project, originally started by Brian Aker

Baidu

Oracle

Yanza

Initial release

2008

2018

1980

2015

Current release

7.2.4, September 2012

0.9

23c, September 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux
macOS
Unix

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

Windows

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

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

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

C
C++
Java
PHP

Groovy
Java
Python

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

PL/SQL

also stored procedures in Java possible

Triggers

hooks for callbacks inside the server can be used.

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Multi-source replication
Source-replica replication

none

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

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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'

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users, roles and permissions

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.