DBMS > 4D vs. PostGIS vs. STSdb

System Properties Comparison 4D vs. PostGIS vs. STSdb

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

Spatial extension of PostgreSQL

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.4d.com

postgis.net

github.com/STSSoft/STSdb4

Technical documentation

developer.4d.com

postgis.net/documentation

Developer

4D, Inc

STS Soft SC

Initial release

1984

2005

2011

Current release

v20, April 2023

3.4.2, February 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

GPLv2, 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

Server operating systems

OS X
Windows

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.NET Client API

Supported programming languages

4D proprietary IDE
PHP

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

based on PostgreSQL

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

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.

User concepts

Access control

Users and groups

yes

based on PostgreSQL

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Share this page