Architecture

This section documents the system architecture of the PROMPT 2 platform.

The platform consists of:

• A React-based web client written in TypeScript

• A Golang-based core server

• Independently deployed course phase services, each with a microfrontend and, optionally, a backend microservice

• A Keycloak instance for identity and access management

Each chapter below describes a key architectural concern.

---

• 📦 Subsystem Decomposition
  • 🧩 Overview
  • ⚙️ Core Subsystems
    • 🖥️ Prompt Core Server
    • 🧑‍🎓 Course Phase Services
    • 🌐 Prompt Core Client
  • 🛠️ Technology Stack
  • 🧭 Responsibilities Breakdown
• 🚀 Deployment Architecture
  • 🧱 Core Components
    • 🖥️ Prompt Core Server
    • 🌐 Prompt Core Client
  • 🧩 Course Phase Services
    • 1. Client-Only Course Phase Services
    • 2. Client-and-Server Course Phase Services
• 🔐 Access Control
  • 🎓 Access Roles
  • 🧩 Role Resolution and Enforcement
    • 🔐 System-Wide Roles: Prompt Administrator and Prompt Lecturer
    • 📘 Course-Specific Roles: Course Lecturer and Course Editor
    • 🧪 Example: Course Lecturer Access Flow
  • 👩‍🎓 Student Role and Phase Participation
    • 🧪 Example: Course Student Access Flow
  • 🎯 Custom Roles for Fine-Grained Access
  • ✅ Summary
• 🗃️ Data Storage and Inter-Phase Communication
  • 🧱 Data Storage Options
    • 1. 🔹 Core Storage
    • 2. 🔸 Custom Storage
  • 🔄 Inter-Phase Communication Schema
    • 📋 DTO Definitions and Registration
      • 📦 Output DTO Schema
  • 🔀 Data Flow Configuration
  • 🌐 Required Service Endpoints
    • 📘 Participation-Level DTOs
    • 📗 Course Phase-Level DTOs
  • 🔐 Access Control for DTO Endpoints
  • ⚠️ Availability and Responsibility