DBMS > PostGIS vs. SwayDB vs. ToroDB

System Properties Comparison PostGIS vs. SwayDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial extension of PostgreSQL

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Spatial DBMS

Key-value store

Document store

Secondary database models

Relational DBMS

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

Score	20.56
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#387	Overall
	#61	Key-value stores

Website

postgis.net

swaydb.simer.au

github.com/torodb/server

Technical documentation

postgis.net/documentation

Developer

Simer Plaha

8Kdata

Initial release

2005

2018

2016

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

GNU Affero GPL V3.0

Open Source

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

Scala

Java

Server operating systems

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

Supported programming languages

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

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

yes

based on PostgreSQL

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.