DBMS > NebulaGraph vs. OpenEdge vs. PostgreSQL vs. SingleStore vs. SQLite

System Properties Comparison NebulaGraph vs. OpenEdge vs. PostgreSQL vs. SingleStore vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A distributed, linear scalable, high perfomant Graph DBMS

Application development environment with integrated database management system

Widely used open source RDBMS

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS

Relational DBMS

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

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	1.75
Rank	#128	Overall
	#11	Graph DBMS

Score	3.49
Rank	#75	Overall
	#39	Relational DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	3.69
Rank	#70	Overall
	#37	Relational DBMS

Score	117.77
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.progress.com/openedge

www.postgresql.org

www.singlestore.com

www.sqlite.org

Technical documentation

docs.nebula-graph.io

documentation.progress.com/output/ua/OpenEdge_latest

www.postgresql.org/docs

docs.singlestore.com

www.sqlite.org/docs.html

Developer

Vesoft Inc.

Progress Software Corporation

PostgreSQL Global Development Group

www.postgresql.org/developer

SingleStore Inc.

Dwayne Richard Hipp

Initial release

2019

1984

1989

1989: Postgres, 1996: PostgreSQL

2013

2000

Current release

OpenEdge 12.2, March 2020

16.4, August 2024

8.5, January 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0 + Common Clause 1.0

commercial

Open Source

BSD

commercial

free developer edition available

Open Source

Public Domain

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

C++

C++, Go

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

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

Linux

64 bit version required

server-less

Data scheme

Strong typed schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language

yes

close to SQL 92

yes

standard with numerous extensions

yes

but no triggers and foreign keys

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC

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

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C++
Go
Java
PHP
Python

Progress proprietary ABL (Advanced Business Language)

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Bash
C
C#
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

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

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Causal Clustering using Raft protocol

Source-replica replication

other methods possible by using 3rd party extensions

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

using RocksDB

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Role-based access control

Users and groups

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

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.