DBMS > OrigoDB vs. SpatiaLite vs. Stardog vs. XTDB

System Properties Comparison OrigoDB vs. SpatiaLite vs. Stardog vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

Spatial extension of SQLite

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Object oriented DBMS

Spatial DBMS

Graph DBMS
RDF store

Document store

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

www.stardog.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

docs.stardog.com

www.xtdb.com/docs

Developer

Robert Friberg et al

Alessandro Furieri

Stardog-Union

Juxt Ltd.

Initial release

2009

under the name LiveDB

2008

2010

2019

Current release

5.0.0, August 2020

7.3.0, May 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

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

Open Source

MIT License

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++

Java

Clojure

Server operating systems

Linux
Windows

server-less

Linux
macOS
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free and OWL/RDFS-schema support

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

yes, extensible-data-notation format

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.

can be achieved using .NET

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

yes

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

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
HTTP API
LINQ

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

HTTP REST
JDBC

Supported programming languages

.Net

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Domain Events

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication in HA-Cluster

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

depending on model

yes

relationships in graphs

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

Write ahead log

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 authorization

Access rights for users 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.