DBMS > Apache Derby vs. NebulaGraph vs. PostgreSQL

System Properties Comparison Apache Derby vs. NebulaGraph vs. PostgreSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A distributed, linear scalable, high perfomant Graph DBMS

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	3.04
Rank	#85	Overall
	#46	Relational DBMS

Score	1.75
Rank	#128	Overall
	#11	Graph DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Website

db.apache.org/derby

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

www.postgresql.org

Technical documentation

db.apache.org/derby/manuals/index.html

docs.nebula-graph.io

www.postgresql.org/docs

Developer

Apache Software Foundation

Vesoft Inc.

PostgreSQL Global Development Group

www.postgresql.org/developer

Initial release

1997

2019

1989

1989: Postgres, 1996: PostgreSQL

Current release

10.17.1.0, November 2023

16.4, August 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache Version 2.0 + Common Clause 1.0

Open Source

BSD

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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

Linux

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Data scheme

yes

Strong typed schema

yes

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

specific XML-type available, but no XML query functionality.

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.

yes

SQL

Support of SQL

yes

SQL-like query language

yes

standard with numerous extensions

APIs and other access methods

JDBC

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java

.Net
C++
Go
Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

partitioning by range, list and (since PostgreSQL 11) by hash

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Causal Clustering using Raft protocol

Source-replica replication

other methods possible by using 3rd party extensions

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

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

Role-based access control

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.