Skip to Content
Last modified by Robert Schaub on 2025/12/22 14:32
Show last authors
1 {{mermaid}}
2 graph TB subgraph Interface_Layer["🖥️ Interface Layer"] UI[Web UI<br/>Browse & Submit] API[REST API<br/>Programmatic Access] AUTH[Authentication<br/>& Authorization] end subgraph Processing_Layer["⚙️ Processing Layer"] AKEL[AKEL Pipeline<br/>Parallel Processing<br/>10-18 seconds] BG[Background Jobs<br/>Source Scoring,<br/>Cache, Archival] QM[Quality Monitoring<br/>Automated Checks] end subgraph Data_Layer["💾 Data & Storage Layer"] PG[(PostgreSQL<br/>Primary Database<br/>All Core Data)] REDIS[(Redis<br/>Cache)] S3[(S3<br/>Archives)] end UI --> AUTH API --> AUTH AUTH --> AKEL AUTH --> QM AKEL --> PG AKEL --> REDIS BG --> PG BG --> S3 QM --> PG REDIS --> PG style Interface_Layer fill:#e1f5ff style Processing_Layer fill:#fff4e1 style Data_Layer fill:#f0f0f0 style AKEL fill:#ffcccc style PG fill:#9999ff
3 {{/mermaid}} **Three-Layer Architecture** - Clean separation of concerns: Interface Layer (user interactions), Processing Layer (AKEL + background jobs), Data Layer (PostgreSQL primary + Redis cache + S3 archives). Background scheduler configured by system administrators.