docs: enhance local dev docs, update Docker Compose, and archive old journals

Added Mailpit setup and updated Keycloak configuration in local development runbooks. Improved Docker Compose stability with updated service dependencies and configurations. Archived outdated journal entries and documents for better organization.
2026-01-20 14:00:09 +01:00
parent 5dc8f18201
commit 46361185d0
56 changed files with 596 additions and 1832 deletions
@@ -1,48 +1,10 @@
 ---
-type: Session Log
-date: 2026-01-15
-participants:
-  - Senior Backend Developer
-  - User
-topic: Backend Infrastructure Analysis & Ping Service Hardening
-status: BLOCKED
+type: Journal
+status: ARCHIVED
+owner: Backend Developer
+last_update: 2026-01-20
 ---

-# Session Log: Backend Infrastructure Analysis
+# Backend Infra Analysis (15.01.2026)

-## 1. Context
-The goal was to start "Phase 1: Backend Hardening" for the `ping-service` as defined in the Master Roadmap. The Senior Backend Developer began analyzing the existing infrastructure to ensure a solid foundation before implementing security and resilience features.
-
-## 2. Key Findings & Analysis
-A deep dive into `backend/infrastructure` revealed significant inconsistencies:
-
-*   **Persistence Conflict (Blocker):**
-    *   `ping-service` is configured for **JPA/Hibernate** (`spring-boot-starter-data-jpa`).
-    *   The shared library `backend/infrastructure/persistence` (specifically `DatabaseUtils.kt`) is built exclusively for **Exposed** (Kotlin SQL Framework).
-    *   This creates a "split-brain" situation regarding ORM strategy.
-
-*   **Missing Security Infrastructure:**
-    *   No shared security module exists (`backend/infrastructure/security`).
-    *   Implementing OAuth2/RBAC directly in `ping-service` would violate DRY principles.
-
-*   **Messaging Overhead:**
-    *   `backend/infrastructure/messaging` includes heavy Kafka dependencies.
-    *   It is unclear if the "Tracer Bullet" (Ping Service) requires Kafka or if a simple REST-based Delta-Sync is sufficient.
-
-## 3. Actions Taken
-*   Analyzed `build.gradle.kts` of `ping-service` and infrastructure modules.
-*   Identified the blocking architectural questions.
-*   **Created Pending ADR:** `docs/01_Architecture/adr/000-PENDING-backend-infrastructure-decisions.md` containing a catalog of questions for the Lead Architect.
-
-## 4. Next Steps
-*   **WAITING FOR:** Lead Architect to resolve the JPA vs. Exposed decision.
-*   **WAITING FOR:** Decision on extracting a shared security module.
-*   Once decisions are made, the Backend Developer will proceed with:
-    1.  Refactoring persistence (either removing JPA or rewriting infrastructure).
-    2.  Implementing the Security Hardening.
-
-## 5. Artifacts Created
-*   `docs/01_Architecture/adr/000-PENDING-backend-infrastructure-decisions.md`
-
---
-*Logged by: Documentation & Knowledge Curator (Proxy)*
+**MOVED:** This file has been archived to `_archive/2026-01-15_Backend_Infrastructure_Analysis.md`.