DBMS > 4D vs. Amazon Redshift vs. PostGIS vs. SiteWhere

System Properties Comparison 4D vs. Amazon Redshift vs. PostGIS vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Large scale data warehouse service for use with business intelligence tools

Spatial extension of PostgreSQL

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.4d.com

aws.amazon.com/redshift

postgis.net

github.com/sitewhere/sitewhere

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

postgis.net/documentation

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Amazon (based on PostgreSQL)

SiteWhere

Initial release

1984

2012

2005

2010

Current release

v20, April 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

OS X
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

Server-side scripts

Stored procedures

yes

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

based on PostgreSQL

selectable replication factor

based on HBase

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

informational only, not enforced by the system

yes

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

In-memory capabilities

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

yes

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

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.