DBMS > 4D vs. EJDB vs. Microsoft SQL Server vs. PostGIS

System Properties Comparison 4D vs. EJDB vs. Microsoft SQL Server vs. PostGIS

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Microsofts flagship relational DBMS

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.4d.com

github.com/Softmotions/ejdb

www.microsoft.com/en-us/sql-server

postgis.net

Technical documentation

developer.4d.com

github.com/Softmotions/ejdb/blob/master/README.md

learn.microsoft.com/en-US/sql/sql-server

postgis.net/documentation

Developer

4D, Inc

Softmotions

Microsoft

Initial release

1984

2012

1989

2005

Current release

v20, April 2023

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

restricted free version is available

Open Source

GPL v2.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

C++

Server operating systems

OS X
Windows

server-less

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

in-process shared library

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

4D proprietary IDE
PHP

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

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

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

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.