DBMS > 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. Blazegraph vs. Citus

System Properties Comparison 4D vs. Amazon Redshift vs. Atos Standard Common Repository vs. Blazegraph vs. Citus

Editorial information provided by DB-Engines

Name

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

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Secondary database models

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	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Website

www.4d.com

aws.amazon.com/redshift

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

blazegraph.com

www.citusdata.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

wiki.blazegraph.com

docs.citusdata.com

Developer

4D, Inc

Amazon (based on PostgreSQL)

Atos Convergence Creators

Blazegraph

Initial release

1984

2012

2016

2006

2010

Current release

v20, April 2023

1703

2.1.5, March 2019

8.1, December 2018

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

AGPL, commercial license also available

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

Linux
OS X
Windows

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

yes

RDF literal 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

specific XML type available, but no XML query functionality

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

does not fully support an SQL-standard

SPARQL is used as query language

yes

standard, with numerous extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC

LDAP

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

4D proprietary IDE
PHP

All languages supporting JDBC/ODBC

All languages with LDAP bindings

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

other methods possible by using 3rd party extensions

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

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

LDAP bind authentication

Security and Authentication via Web Application Container (Tomcat, Jetty)

fine grained access rights according to SQL-standard

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.