The Java client currently fails on a clean startup if the database is unavailable at service start.
We need to add resilience for database connectivity in two scenarios:
- Runtime disconnect — automatically recover the DB connection when it is lost during normal operation.
- Startup failure — if DB is unavailable on startup, the service should either:
- keep retrying connection with backoff until success, or
- restart gracefully (based on agreed operational strategy).
The Java client currently fails on a clean startup if the database is unavailable at service start.
We need to add resilience for database connectivity in two scenarios: