DBMS > GraphDB vs. Postgres-XL vs. SQLite

System Properties Comparison GraphDB vs. Postgres-XL vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	3.32
Rank	#91	Overall
	#6	Graph DBMS
	#4	RDF stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.ontotext.com

www.postgres-xl.org

www.sqlite.org

Technical documentation

graphdb.ontotext.com/documentation

www.postgres-xl.org/documentation

www.sqlite.org/docs.html

Social network pages

Developer

Ontotext

Dwayne Richard Hipp

Initial release

2000

2014

since 2012, originally named StormDB

2000

Current release

10.4, October 2023

10 R1, October 2018

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

Open Source

Mozilla public license

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.

Implementation language

Java

Server operating systems

All OS with a Java VM
Linux
OS X
Windows

Linux
macOS

server-less

Data scheme

schema-free and OWL/RDFS-schema support; RDF shapes

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

XML type, but no XML query functionality

Secondary indexes

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

distributed, parallel query execution

yes

SQL-92 is not fully supported

APIs and other access methods

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

well-defined plugin interfaces; JavaScript server-side extensibility

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Migrating From LPG to RDF Graph Model
8 May 2024

Case study: Policy Enforcement Automation With Semantics
2 May 2024

Okay, RAG… We Have a Problem
26 April 2024

Scaling Understanding with the Help of Feedback Loops, Knowledge Graphs and NLP
19 April 2024

How Knowledge Graphs Power Data Mesh and Data Fabric
10 April 2024

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.