DBMS > 4D vs. Amazon Redshift vs. CockroachDB vs. FatDB vs. ToroDB

System Properties Comparison 4D vs. Amazon Redshift vs. CockroachDB vs. FatDB vs. ToroDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

Large scale data warehouse service for use with business intelligence tools

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Document store

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	6.15
Rank	#55	Overall
	#33	Relational DBMS

Website

www.4d.com

aws.amazon.com/redshift

www.cockroachlabs.com

github.com/torodb/server

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

Developer

4D, Inc

Amazon (based on PostgreSQL)

Cockroach Labs

FatCloud

8Kdata

Initial release

1984

2012

2015

2012

2016

Current release

v20, April 2023

23.1.1, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

Open Source

AGPL-V3

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
macOS
Windows

Windows

All OS with a Java 7 VM

Data scheme

yes

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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, wire compatible with PostgreSQL

Via inetgration in SQL Server

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication using RAFT

selectable replication factor

Source-replica replication

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

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

Role-based access control

Can implement custom security layer via applications

Access rights for users and roles

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.