DBMS > 4D vs. Couchbase vs. PlanetScale vs. PostGIS

System Properties Comparison 4D vs. Couchbase vs. PlanetScale 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

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Website

Technical documentation

developer.4d.com

docs.couchbase.com

planetscale.com/docs

postgis.net/documentation

Developer

4D, Inc

Couchbase, Inc.

PlanetScale

Initial release

1984

2011

2020

2005

Current release

v20, April 2023

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

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

C, C++, Go and Erlang

Server operating systems

OS X
Windows

Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

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

close to SQL 92

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

with proprietary extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

4D proprietary IDE
PHP

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

proprietary syntax

user defined functions

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Ephemeral buckets

yes

User concepts

Access control

Users and groups

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Users with fine-grained authorization concept

no user groups or roles

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.