feat(sync): implement Delta-Sync API and update clients to support offline-first workflow

Added `/ping/sync` endpoint with timestamp-based Delta-Sync functionality to efficiently support offline-first clients. Extended `PingApi` and frontend clients (`PingApiClient`, `PingApiKoinClient`) with `syncPings`. Updated repository, service, and controller logic for sync handling, including new JPA query `findByCreatedAtAfter`. Adjusted test doubles and completed unit tests for backend and frontend alignment. Documented sync approach and API usage.
This commit is contained in:
2026-01-17 12:22:16 +01:00
parent 59568a42d8
commit 351fe7a672
15 changed files with 190 additions and 62 deletions
+7
View File
@@ -17,6 +17,7 @@ Der `ping-service` ist der "Tracer Bullet" Service für die Meldestelle-Architek
| GET | `/ping/secure` | Geschützter Endpoint (benötigt Rolle) | **Secure** (MELD_USER) |
| GET | `/ping/health` | Health Check | Public |
| GET | `/ping/history` | Historie aller Pings | Public (Debug) |
| GET | `/ping/sync` | Delta-Sync für Offline-Clients | Public |
## Architektur
Der Service folgt der Hexagonalen Architektur (Ports & Adapters):
@@ -36,3 +37,9 @@ Der Service folgt der Hexagonalen Architektur (Ports & Adapters):
## Resilience
* Circuit Breaker: Resilience4j (für DB-Zugriffe und simulierte Fehler).
## Sync-Strategie (Phase 3)
* Implementiert Delta-Sync via `/ping/sync`.
* Parameter: `lastSyncTimestamp` (Long, Epoch Millis).
* Response: Liste von `PingEvent` (ID, Message, LastModified).
* Client kann basierend auf dem Timestamp nur neue/geänderte Daten abrufen.