DBMS > PostGIS vs. SQLite vs. Stardog vs. TerminusDB

System Properties Comparison PostGIS vs. SQLite vs. Stardog vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Relational DBMS

Document store
RDF store

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

Technical documentation

postgis.net/documentation

www.sqlite.org/docs.html

docs.stardog.com

terminusdb.github.io/terminusdb/#

Developer

Dwayne Richard Hipp

Stardog-Union

DataChemist Ltd.

Initial release

2005

2000

2010

2018

Current release

3.4.2, February 2024

3.46.0 (23 May 2024), May 2024

7.3.0, May 2020

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Public Domain

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

server-less

Linux
macOS
Windows

Linux

Data scheme

yes

dynamic column types

schema-free and OWL/RDFS-schema support

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

SQL-92 is not fully supported

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

yes

Triggers

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

none

Multi-source replication in HA-Cluster

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

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

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

yes

based on PostgreSQL

Access rights for users and roles

Role-based access control

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.