DBMS > 4D vs. jBASE vs. Microsoft Azure Cosmos DB vs. PostGIS vs. SiteWhere

System Properties Comparison 4D vs. jBASE vs. Microsoft Azure Cosmos DB vs. PostGIS vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A robust multi-value DBMS comprising development tools and middleware

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Multivalue DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

www.4d.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

azure.microsoft.com/services/cosmos-db

postgis.net

github.com/sitewhere/sitewhere

Technical documentation

developer.4d.com

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Rocket Software (formerly Zumasys)

Microsoft

SiteWhere

Initial release

1984

1991

2014

2005

2010

Current release

v20, April 2023

5.7

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

AIX
Linux
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

optional

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

close to SQL 92

Embedded SQL for jBASE in BASIC

SQL-like query language

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

.Net
Basic
Jabbascript
Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

JavaScript

user defined functions

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

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.