Vdm Healthcheck Bundle Laravel Package

Product Decisions This Supports

• Observability & Reliability: Enables standardized /liveness and /readiness endpoints for Kubernetes/containerized deployments, reducing operational overhead for infrastructure teams.
• DevOps Alignment: Accelerates compliance with platform engineering requirements (e.g., "all services must expose healthchecks") without custom development.
• Cost-Effective Build vs. Buy: Avoids reinventing healthcheck logic for PHP/Laravel apps, saving ~10–20 dev hours per project.
• Use Cases:
  • Microservices architectures needing quick health signal validation.
  • CI/CD pipelines requiring pre-deployment readiness verification.
  • Multi-region deployments where dependency checks (e.g., DB, cache) are critical.

When to Consider This Package

• Adopt if:

  • Your Laravel/PHP app runs in Kubernetes, Docker Swarm, or similar orchestration requiring liveness/readiness probes.
  • You lack a centralized healthcheck solution and need minimal setup (config-only, no custom code).
  • Your team prioritizes standardized endpoints over custom implementations (e.g., /health vs. /status).
  • You need basic dependency checks (e.g., database connectivity) without complex monitoring tools.

• Look elsewhere if:

  • You require advanced metrics (e.g., latency, error rates) → Use Prometheus + Blackbox Exporter.
  • Your stack includes non-PHP services → Consider a service mesh (Istio) or platform-native probes.
  • You need custom business logic in healthchecks → Extend with Laravel’s service container or build in-house.
  • Your team prefers zero-config solutions → Evaluate existing Laravel packages like spatie/laravel-health (more stars, active maintenance).

How to Pitch It (Stakeholders)

To Executives: "This package eliminates a common DevOps bottleneck by providing pre-built, Kubernetes-compatible healthcheck endpoints for our Laravel apps in just 15 minutes. It reduces operational toil by standardizing /liveness and /readiness probes—critical for scaling our microservices—while keeping costs low (MIT license, no vendor lock-in). Similar to how we’d use a library for logging or auth, this handles a repetitive infrastructure task so our team can focus on core features."

To Engineering: *"The VdmHealthcheckBundle gives us:

• Two endpoints out of the box: /liveness (crash detection) and /readiness (traffic routing safety).
• Config-driven dependency checks: Add DB, Redis, or API calls to readiness_checkers without writing controllers.
• Secret-protected details: Hide verbose output behind a header/param for security.
• Zero Laravel version lock: Works with modern PHP/Laravel setups (tested with Symfony components).

Tradeoffs:

• Not feature-rich (e.g., no Prometheus metrics), but extensible via Laravel’s service container.
• Smaller community (1 star) but recently updated (March 2024) and MIT-licensed.

Proposal: Pilot in [Service X] to replace ad-hoc healthchecks, then roll out to other PHP services. If we hit limits, we can extend it or switch to a more mature package later."*