Dev's 60-second deploy check flagged a healthy site as broken just days after launch

·2 views

A developer published a deploy verification tool on Monday with a 60-second propagation tolerance, only to see it misfire on Wednesday when a deploy took between 40 and 70 seconds to complete. The false alarm occurred because the check was designed around a small sample of roughly three deploys and an arbitrary 20-second retry interval. Logging actual deploy times revealed a tenfold spread — from 6.7 to 70 seconds — making any single fixed timeout unreliable. The incident also exposed a deeper flaw: the checker treats a partially propagated deploy, where a listing page is live but the linked article returns a 404, the same as a deploy that has not started at all. The developer argues that simply raising the timeout would repeat the same unscientific approach, and that the real problem is relying on a single threshold to describe what is actually a multi-file, non-atomic process.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Python Multithreading Is Not Fake — But It Depends on the Task

A developer noticed significant speed gains after parallelizing a network data-fetching tool with Python threads, despite a colleague's claim that Python multithreading is 'fake' due to the Global Interpreter Lock (GIL). The GIL restricts Python so that only one thread executes bytecode at a time, which led to the misconception. However, the GIL is released during I/O waits, allowing other threads to run while one waits for a network response, which explains the real speedup observed. For CPU-bound tasks like image processing or heavy math, the GIL never releases meaningfully, making multithreading genuinely ineffective. The key distinction is that Python threads deliver real concurrency for I/O-bound work but not for CPU-bound operations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Guide: How to Embed Virtual Cards via Partner API in 2026

A technical guide aimed at backend engineers outlines the key considerations for integrating virtual card issuance through partner APIs rather than building in-house. It covers critical architecture decisions including authentication flows, idempotency handling, and webhook design to prevent errors like duplicate card issuance. The guide highlights that white-label card API providers allow companies to plug into card programs without needing an EMI license or a full compliance department. A dedicated section addresses crypto-funded cards, noting that converting assets like BTC or USDT into spendable balances introduces unique failure modes absent in fiat-only systems. The guide also distinguishes card issuing APIs from broader Banking-as-a-Service platforms, emphasizing the importance of correctly scoping the integration from the outset.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Lightweight API Integration Proxy Using Django to Simplify Auth and Logging

A developer has created a lightweight API integration proxy called Asstgr, built on Django and PostgreSQL, to streamline how applications interact with multiple third-party APIs. The tool consolidates authentication, execution, and logging into a single layer, so applications can focus purely on business logic rather than managing per-API credentials and formats. The synchronous MVP uses the Requests library to dynamically construct downstream API calls via a unified execution endpoint. The developer chose Django for rapid prototyping and plans to migrate to asynchronous frameworks such as FastAPI or Go once the core logic is stable. Upcoming features include payload encryption, async execution via HTTPX, and caching with Redis.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Key AWS S3 concepts developers need to understand for production use

Amazon S3 is a widely used object storage service where files are stored as objects inside buckets, each identified by a unique key string. Access is private by default and should be managed through IAM policies or bucket policies, with presigned URLs recommended for secure client-side uploads rather than granting broad bucket access. Since 2020, S3 offers strong consistency for all operations, meaning objects can be read or listed immediately after being written. S3 offers multiple storage classes such as Standard, Intelligent-Tiering, and Glacier, and lifecycle rules can automatically move data between tiers to reduce costs. Enabling versioning protects against accidental deletions and overwrites, though it increases storage costs and should be paired with lifecycle rules to manage old versions.

0 comments Read more at DEV Community