HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Untitled Lesson

⚡ Total XP: 0|💻 backend XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Configuring a HEALTHCHECK with no start-period grace window for an application with meaningful startup time

// Wrong: failures count immediately, even during normal startup
HEALTHCHECK --interval=30s --retries=3 CMD curl -f http://localhost:3000/health

// Correct: a grace period covering typical startup time
HEALTHCHECK --interval=30s --retries=3 --start-period=40s CMD curl -f http://localhost:3000/health

The Solution //

Without a start-period, health check failures begin counting immediately, even while the application is still legitimately starting up (running migrations, warming caches) — this can cause a healthy, normally-starting application to be prematurely marked unhealthy and restarted, potentially in a repeating loop that never lets it finish starting.

The Error //

Implementing an expensive, unbounded operation inside a health check endpoint that runs on a frequent interval

// Wrong: expensive, unbounded operation run every 30 seconds forever
app.get("/health", async (req, res) => { await db.query("SELECT COUNT(*) FROM huge_table"); });

// Correct: fast, bounded, appropriately timed out
app.get("/health", async (req, res) => { await db.query("SELECT 1", { timeout: 2000 }); });

The Solution //

A health check runs repeatedly, indefinitely, for as long as the container is alive — if the check itself performs an expensive, unbounded operation (a full unindexed query, an external API call with no timeout), it adds unnecessary ongoing load and can itself become unreliable or slow, undermining the very health signal it's meant to provide.