Advanced Health Check Endpoint

[nursetechie]

Issue #40 — feat: Advanced Health Check Endpoint

Description

The basic /health endpoint is insufficient for Kubernetes readiness probes, as it returns success even if the database is down. An advanced health check validates downstream dependencies, preventing traffic from routing to broken instances.

---

Requirements & Context

Architectural Goal: Enable accurate container orchestration readiness probes.

Implementation Expectations: Update the /health endpoint to query the Prisma database connection and the Stellar RPC node. Return an HTTP 503 if any critical dependency is offline.

---

Acceptance Criteria

• The endpoint accurately reflects the health of external dependencies.
• HTTP status codes accurately distinguish between healthy (200) and degraded (503) states.

---

Out of Scope

• Implementing complex retries for the health check itself.

---

Suggested Execution

git checkout -b feat/advanced-health-check

---

Suggested Commit Message

feat: implement advanced health check verifying database and rpc connectivity

---

Testing Notes

• Turn off the local PostgreSQL database and verify the endpoint responds with a 503 HTTP code.

---

References

Kubernetes Liveness and Readiness Probe best practices.

---

Definition of Done

• Ready for review.

[OpensrcLord]

Hello @maintainer, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me. And I will deliver at the shortest possible time.

[Bolajiomo99]

Hi team, I'd like to claim the final slot for this issue. I can update the /health endpoint to serve as an accurate Kubernetes readiness probe by validating both Prisma DB connectivity and the Stellar RPC node status. I will ensure it correctly handles errors and returns an HTTP 503 during partial outages, adhering precisely to your suggested git workflows and commit naming conventions. Ready to push a clean PR.