DBMS > PostGIS vs. SiteWhere vs. SwayDB

System Properties Comparison PostGIS vs. SiteWhere vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

M2M integration platform for persisting/querying time series data

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

Primary database model

Spatial DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

postgis.net

github.com/sitewhere/sitewhere

swaydb.simer.au

Technical documentation

postgis.net/documentation

sitewhere1.sitewhere.io/index.html

Developer

SiteWhere

Simer Plaha

Initial release

2005

2010

2018

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

Linux
OS X
Windows

Data scheme

yes

predefined scheme

schema-free

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

HTTP REST

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

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

based on HBase

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

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

Users with fine-grained authorization concept

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page