DBMS > Apache Drill vs. Heroic vs. HugeGraph vs. Oracle

System Properties Comparison Apache Drill vs. Heroic vs. HugeGraph vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A fast-speed and highly-scalable Graph DBMS

Widely used RDBMS

Primary database model

Document store
Relational DBMS

Time Series DBMS

Graph DBMS

Relational DBMS

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	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	0.15
Rank	#339	Overall
	#33	Graph DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Website

drill.apache.org

github.com/spotify/heroic

github.com/hugegraph
hugegraph.apache.org

www.oracle.com/database

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

hugegraph.apache.org/docs

docs.oracle.com/en/database

Developer

Apache Software Foundation

Spotify

Baidu

Oracle

Initial release

2012

2014

2018

1980

Current release

1.20.3, January 2023

0.9

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

restricted free version is 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.

Implementation language

Java

C and C++

Server operating systems

Linux
OS X
Windows

Linux
macOS
Unix

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

via Elasticsearch

yes

also supports composite index and range index

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C++

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

Server-side scripts

Stored procedures

user defined functions

asynchronous Gremlin script jobs

PL/SQL

also stored procedures in Java possible

Triggers

yes

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

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

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

User concepts

Access control

Depending on the underlying data source

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.