Technical
Retry failed emails without flooding the SMTP server
Retrying all failed emails at once after an SMTP outage guarantees a second incident — blacklist, rate limit and saturated mailboxes. The queue needs a backoff strategy.
No results for this search
Technical
Locking a cron job: avoid two identical runs at once
A cron that exceeds its interval, a deployment that restarts workers, DST handled badly — without a lock, you duplicate invoices, emails or imports without noticing.
Technical
Elasticsearch: size indexing without stealing application RAM
Elasticsearch is hungry for heap and I/O. On a VPS shared with your app, a poorly tuned reindex can OOM-kill your PHP or Node process overnight.
Technical
Meilisearch: deploy fast search with a consistent backup
Meilisearch is light and quick to install — but snapshot backup and recovery need discipline many Docker deployments skip until the first index loss.
Technical
Proxy timeout: keep WebSockets from dropping after one minute
A chat, real-time dashboard or online game that disconnects every 60 seconds often points to a misconfigured proxy — not your WebSocket code.
Technical
QUIC and UDP: check the firewall before enabling HTTP/3
HTTP/3 runs on QUIC over UDP. If firewall or host blocks UDP 443, clients silently fall back to HTTP/2 — or fail without clear message.
Technical
TCP keepalive: retain useful connections without letting them die
Long-lived connections die silently when a NAT or load balancer cuts idle flows. TCP keepalive detects that — provided you do not confuse it with application heartbeats.
Technical
Network MTU: diagnose pages that fail for no visible reason
Some pages load on Wi-Fi but not on 4G, or stall after the first MB. Often the culprit is MTU or broken PMTUD — not your application.
Technical
AAAA records: publish IPv6 without making the site unreachable
Adding an AAAA without checking the full stack can break access for some visitors. Here is how to enable IPv6 without timeouts or blank pages.
Technical
Vulnerable dependencies: handle alerts by actual exposure
A scanner reporting 200 CVEs does not tell you which ones touch your attack surface. Here is how to prioritise fixes by real exposure, not raw scores.
Technical
Content Security Policy: deploy a barrier without breaking the front end
A strict CSP header on Friday night and Stripe checkout vanishes: the XSS barrier only ships via report-only → enforce, with marketing in the loop.
Technical
CORS: fix browser access without opening the API to the world
CORS console error: not the API lock but browser policy — origin whitelist, OPTIONS preflight, and independent auth.
Technical
Certificate pinning: why a good intention can block a website
After Let's Encrypt renewal, the mobile app may stay offline: pinning on the old key without backup pin blocks the whole fleet.
Technical
Migrating a database: sequence schema, data, and traffic
Midnight cutover without schema/data parity: sequence expand/contract, sync and traffic — clone dry-run before prod window.
Technical
rsync: options that prevent a destructive synchronization
A reversed rsync cron wipes prod: trailing slash, --delete, and written SRC→DST direction prevent destructive sync.
Technical
Immutable backups: the safeguard that must also be restorable
Object Lock blocks ransomware on copies — only if you proved restore before trusting immutability.
Technical
Granular restore: recover one customer without rewinding everyone
Restoring the whole VM for one customer erases everyone's timeline: granular restore requires tenant architecture and semiannual drills.
Technical
Encrypting backups: protect copies as much as production
Prod encrypted at rest, backups land plaintext in a shared bucket: one compromised credential exposes full history.
Technical
S3 presigned URLs: grant temporary access without an expensive proxy
Serving 10 GB user exports through PHP would saturate CPU. Presigned URLs delegate download to storage — with an expiry date you must not forget.
Technical
Object storage lifecycle rules: automate archiving without losing data
The S3 bill doubles quietly: millions of never-read objects sit in Standard tier. Lifecycle rules automate archiving — if you test them.
Technical
IOPS: connect storage promises to perceived slowness
VPS sheet promises NVMe SSD. In prod PostgreSQL checkpoint chokes: 300 sustained IOPS, not 100k marketing burst.
Technical
CPU steal on a VPS: identify noisy-neighbor contention
API latency rises with no deploy or traffic spike: `%steal` at 15% in top. Your VPS waits for CPU the hypervisor gives a neighbor.
Technical
Server swap: warning sign, safety net, or bad habit?
Monitoring shows 2 GB swap used permanently: panic or normal? Depends on cold cache vs genuinely missing RAM.
Technical
Exhausted inodes: why disk space can look available
df -h shows 40% free yet you cannot create a file: inodes exhausted. Classic after millions of cache or session files.