DBMS > 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. FatDB vs. Sqrrl

System Properties Comparison 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. FatDB vs. Sqrrl

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed 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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column 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

Website

www.4d.com

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

sqrrl.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

Developer

4D, Inc

Amazon (based on PostgreSQL)

Atos Convergence Creators

FatCloud

Amazon

originally Sqrrl Data, Inc.

Initial release

1984

2012

2016

2012

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

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

Windows

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

LDAP

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

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

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

cell division

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic execution of specific operations

Atomic updates per row, document, or graph entity

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

LDAP bind authentication

Can implement custom security layer via applications

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.