Page Comparison

Name

Description

Alternatives

Cert Manager

Creates SSL/TLS certificates to access the web applications. Uses Letsencrypt certificates by default.

Catalog Server

Creates RADAR-base topics in Kafka, registers schemas in Schema Registry and keeps a catalog of available source types.

Kafka

All real-world data in RADAR-base goes through Kafka, an advanced message broker. Data is stored there for processing by other applications, like real-time analysis or long-term data storage. Data remains for a limited time (usually a month).

Confluent Cloud

Amazon MSK

Management Portal

Portal to manage projects and participants throughout RADAR-base.

Nginx Ingress

Web server used for accessing web applications.

PostgreSQL

Database used to store Management Portal data.

Amazon RDS for PostgreSQL

Dedicated PostgreSQL server

Radar Output

Reads data from an intermediate object storage and converts it to a RADAR-base oriented output directory, by organizing it by project, user and collection date.

Radar S3 connector

Reads raw participants data from Kafka and puts them into an intermediate object storage like AWS S3 or Minio.

Redis

Used by Radar Output to coordinate data processing in a parallel way.

RADAR Gateway

REST Gateway to Kafka, for incoming participant data. It performs authentication, authorization, content validation and decompression.

SMTP

Email server for sending registration email to researchers and participants.

Kafka Schema Registry

Registry of Avro Schema’s used in a RADAR-base installation. Validation layer on top of Kafka to structurally verify incoming data.

Confluent Cloud

Zookeeper

Use for Kafka cluster management and coordination.

Confluent Cloud