DBMS > Apache Impala vs. MySQL vs. NebulaGraph

System Properties Comparison Apache Impala vs. MySQL vs. NebulaGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Widely used open source RDBMS

A distributed, linear scalable, high perfomant Graph DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	12.57
Rank	#40	Overall
	#24	Relational DBMS

Score	1039.46
Rank	#2	Overall
	#2	Relational DBMS

Score	2.01
Rank	#120	Overall
	#11	Graph DBMS

Website

impala.apache.org

www.mysql.com

github.com/vesoft-inc/nebula
www.nebula-graph.io

Technical documentation

impala.apache.org/impala-docs.html

dev.mysql.com/doc

docs.nebula-graph.io

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Oracle

since 2010, originally MySQL AB, then Sun

Vesoft Inc.

Initial release

2013

1995

2019

Current release

4.1.0, June 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0 + Common Clause 1.0

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

C++

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Strong typed schema

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

Nebula Graph internally uses the Key-Value store RocksDB for persistency. The vertices, edges, and their properties are stored as Key while their values are stored as Value. The primary indexes are per Key and secondary indexes are per Value.

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Browser interface
console (shell)
Cypher Query Language
GO Object Graph Mapper
Java Object Graph Mapper
NGBatis

ORM framework for NebulaGraph and Spring-Boot
Proprietary native API
Python Object Graph Mapper
Query language nGQL

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C++
Go
Java
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Causal Clustering using Raft protocol

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

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

using RocksDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

More information provided by the system vendor

Specific characteristics

NebulaGraph is a truly distributed, linearly scalable, lightning-fast graph database,...
» more

Competitive advantages

NebulaGraph boasts the world's only graph database solution that is able to host...
» more

Typical application scenarios

Social networking Fraud detection Knowledge graph Data warehouse management Anti...
» more

Key customers

Companies from a variety of industries have implemented NebulaGraph Database in production,...
» more

Market metrics

At our very early stage, NebulaGraph has already received over 10,000 stars on GitHub...
» more

Licensing and pricing models

NebulaGraph is open source and free to use under Apache 2.0 license.
» more

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.