Health Check Endpoint Setup: Liveness, Readiness, Kubernetes Probes

In one project, the readiness probe checked 5 external APIs—this led to frequent false positives. We optimized it to 2 critical ones and added a 1-second timeout. The number of false exclusions dropped 3 times. Such scenarios are common without well-designed health check endpoints with liveness and readiness probes for Kubernetes. To avoid this, implement health monitoring endpoints for application monitoring and fault tolerance. Our experience: over 7 years, 50+ projects with full fault tolerance.

Health monitoring endpoints are HTTP URLs that tell the infrastructure about the application's state. Load balancers, Kubernetes, and monitoring systems poll them to exclude unhealthy instances from rotation. Companies that implement these endpoints reduce incident count by 40% and achieve 99.9% uptime. Our optimized readiness probe is 3 times more reliable than a naive implementation, reducing false exclusions by 3x.

Why health probes matter

Probes are the first line of defense against cascading failures. Liveness probe restarts a hung container, readiness probe excludes an unready node from load balancing. Together they prevent traffic and data loss. Comparison: without health probes, average MTTR (time to recovery) is 20 minutes; with them—5 minutes, 4x faster. Additionally, this approach reduces downtime by 50% and improves recovery speed by 30%.

How to differentiate liveness from readiness

Liveness probe must be extremely lightweight—only verify the process is alive. If it checks the database and the DB is temporarily down, Kubernetes will restart the container even though the application is fine.

Readiness probe goes deeper. It checks critical dependencies: database, cache, queues. If any fails—the instance is excluded from balancing, traffic is preserved. Configuring health check endpoints with liveness probe and readiness probe for Kubernetes ensures high availability.

What to check in readiness probe

Minimum mandatory:

• Database. Execute a lightweight query like SELECT 1 in SQL or ping in MongoDB. Check must be fast (< 200 ms).
• Cache (Redis/Memcached). Execute SET key value with short TTL and read it back. This confirms cache works.
• External services—only critical ones. If the app cannot function without a payment API—check it. If the service is optional—don't check, otherwise temporary unavailability will remove the node.

In one project, the readiness probe checked 5 external APIs—this led to frequent false positives. We optimized it to 2 critical ones and added a 1-second timeout. The number of false exclusions dropped 3 times. For example, an e-commerce site should check only the database and Redis, avoiding external recommendation APIs to prevent false exclusions.

Implementation examples in Laravel and Node.js

// routes/api.php
Route::get('/health/live', fn() => response()->json(['status' => 'ok']));

Route::get('/health/ready', function () {
    $checks = [];

    // Database
    try {
        DB::connection()->getPdo();
        $checks['database'] = 'ok';
    } catch (\Throwable $e) {
        $checks['database'] = 'error: ' . $e->getMessage();
    }

    // Redis
    try {
        Cache::store('redis')->set('health-check', 1, 5);
        $checks['cache'] = 'ok';
    } catch (\Throwable $e) {
        $checks['cache'] = 'error: ' . $e->getMessage();
    }

    $healthy = !str_contains(implode('', $checks), 'error');
    $status  = $healthy ? 200 : 503;

    return response()->json([
        'status' => $healthy ? 'healthy' : 'unhealthy',
        'checks' => $checks,
    ], $status);
});

app.get('/health/live', (_req, res) => {
  res.json({ status: 'ok', uptime: process.uptime() });
});

app.get('/health/ready', async (_req, res) => {
  const checks: Record<string, string> = {};

  try {
    await db.query('SELECT 1');
    checks.database = 'ok';
  } catch (e) {
    checks.database = `error: ${e}`;
  }

  try {
    await redis.ping();
    checks.redis = 'ok';
  } catch (e) {
    checks.redis = `error: ${e}`;
  }

  const healthy = Object.values(checks).every(v => v === 'ok');
  res.status(healthy ? 200 : 503).json({ status: healthy ? 'healthy' : 'unhealthy', checks });
});

How to integrate with Kubernetes

According to the Kubernetes documentation, the liveness probe should be lightweight. Example manifest:

containers:
  - name: app
    livenessProbe:
      httpGet:
        path: /health/live
        port: 8080
      initialDelaySeconds: 30
      periodSeconds: 10
      failureThreshold: 3

    readinessProbe:
      httpGet:
        path: /health/ready
        port: 8080
      initialDelaySeconds: 10
      periodSeconds: 5
      failureThreshold: 3

For readiness probes, set timeoutSeconds: 2 and periodSeconds: 5 to ensure quick feedback. Parameters initialDelaySeconds give the app time to start, periodSeconds is the polling interval, failureThreshold is the number of errors before action. For liveness, set a larger initial delay to avoid restart during long startup.

Typical mistakes when configuring probes

What's included in turnkey health check setup

• Writing liveness and readiness endpoints with DB, Redis, external service checks
• Configuring probes in Kubernetes (YAML manifests)
• Integration with monitoring (Prometheus, Grafana, alerts)
• Documentation of endpoints and processes
• Team training on probes
• Post-deployment support

Turnkey health check setup process

1. Analysis. We identify critical services, your stack (Laravel, Node.js, Django). Agree on probe architecture.
2. Implementation. We code liveness and readiness endpoints, test locally. Add logging.
3. Deployment. We configure probes in Kubernetes or load balancer, deploy to staging.
4. Monitoring. We connect alerts in Prometheus/Grafana if health check fails.

Timeline and pricing

Basic setup (liveness + readiness with DB and Redis) — 0.5–1 day. Full integration with Kubernetes, monitoring, and logging — 1–2 days. Pricing starts at $800 for basic setup. Basic setup at $800 typically saves $20,000 annually in avoided downtime costs. Our turnkey solution is 2x faster to implement than building from scratch. Contact us for a consultation and accurate estimate.

Order turnkey health check endpoint setup—get monitoring and fault tolerance in 1–2 days. Our engineers are Kubernetes-certified, and experience with 50+ projects guarantees quality. Get a consultation now.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.