DBMS > PostGIS vs. SwayDB vs. Transbase vs. WakandaDB

System Properties Comparison PostGIS vs. SwayDB vs. Transbase vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

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

A resource-optimized, high-performance, universally applicable RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Relational DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

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

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

postgis.net

swaydb.simer.au

www.transaction.de/en/products/transbase.html

wakanda.github.io

Technical documentation

postgis.net/documentation

www.transaction.de/en/products/transbase/features.html

wakanda.github.io/doc

Developer

Simer Plaha

Transaction Software GmbH

Wakanda SAS

Initial release

2005

2018

1987

2012

Current release

3.4.2, February 2024

Transbase 8.3, 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

GNU Affero GPL V3.0

commercial

free development license

Open Source

AGPLv3, extended commercial license available

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

C and C++

C++, JavaScript

Server operating systems

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

Java
Kotlin
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

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

fine grained access rights according to SQL-standard

yes

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.