How Idempotency Keys Prevent Double Charges Caused by Payment Timeouts

When a payment request succeeds on the server but the response never reaches the client due to a connection drop, the customer may retry and get charged twice. Idempotency keys — unique identifiers generated by the client and sent with each request — allow the server to detect and reject duplicate transactions. A naive database check-then-save approach is still vulnerable to race conditions when simultaneous requests arrive within milliseconds of each other. In Laravel, this can be solved using Cache::lock(), which ensures only one request is processed at a time by blocking concurrent duplicates until the first completes. Stored keys should include the original response and be deleted after a set retention window, such as 24 hours, to avoid unnecessary database bloat.

No escape for Trump in hush money case as US judge blocks bid to shift federal court

42 years on, Sukumara Kurup mystery returns with Brunei ‘sighting’ — and a photo twist

Parents Seek Answers After Arrest in Indian Woman's Murder in US

Nikitha Godishala, an Indian woman, was found dead with stab wounds in Columbia, United States, on January 3. She was discovered in the apartment of her ex-boyfriend, Arjun Sharma, who has since been arrested. While her parents have acknowledged the arrest as a breakthrough in the case, they say they still need answers. The family is seeking clarity on the circumstances surrounding their daughter's death.

Edge Caching Can Cut Next.js API Response Times from 240ms to Under 15ms

Next.js App Router's Route Handlers, when deployed on serverless platforms like Vercel or AWS Lambda, often suffer from cold starts and database connection latency that can push response times to over 1,400ms under load. A technical guide published on DEV Community outlines how adding standard RFC 5861 Cache-Control headers and routing API traffic through an edge proxy can dramatically reduce serverless function invocations. By caching read-heavy endpoints at the edge, developers can serve over 95% of API requests without hitting the origin server, cutting median latency to around 11ms. When underlying data changes, cache invalidation can be triggered programmatically via Next.js Server Actions, ensuring users still receive fresh content. The approach is reported to reduce serverless invocations by nearly 96% and cut monthly cloud infrastructure costs by more than 75%.

Nepal needs at least $4 bn for rebuilding: FinMin

Iran War at 6 Months: No End in Sight as Hormuz Shipping Stays Disrupted

Six months into the conflict involving Iran, the situation remains far from resolution despite early predictions of a swift end. Former US President Donald Trump had forecast the war would conclude within four weeks, but that timeline has proven incorrect. Iran has not capitulated, and maritime traffic through the strategically vital Strait of Hormuz continues to face severe disruption. The prolonged conflict is generating wide-ranging consequences spanning politics, energy markets, and global trade. No clear diplomatic or military path toward ending the war has yet emerged.

Nepal Flash Floods Overwhelm Morgues; Unidentified Bodies Reach Indian Border

Devastating flash floods in Nepal have filled district morgues beyond capacity, forcing authorities to convert other buildings into temporary mortuaries. Hundreds of security personnel are actively searching riverbanks to recover more bodies. Remains are being transported between districts to aid in preservation and identification efforts. The flood's impact has crossed into India, with unidentified bodies surfacing in districts along the Gandak river downstream.

Trump's Greenland row shadows Iceland's EU vote

How to Build and Test Transactional Email Receipts Before Picking a Provider

A technical guide published on DEV Community outlines a disciplined approach to designing transactional email receipts, particularly for healthtech payment confirmations. The core advice is to render and test a minimal receipt template locally before evaluating any email API provider such as MailerSend, Amazon SES, or Postmark. Key system decisions — including suppression lists, idempotency keys, and template ownership — should live in the application layer rather than inside a provider's account. The guide warns that switching providers mid-deployment can risk duplicate receipts if business logic is tied to a specific adapter, and recommends a single fixture and pass/fail contract to compare candidates. Privacy compliance, especially avoiding clinical details in receipts, is flagged as a requirement that must be approved by security and compliance teams rather than resolved by a provider checklist.

India News Live updates, 29 August 2026 |CNG price hiked by Rs 3.89/kg in Delhi

Coffee Chains Pivot to Cold, Customisable Drinks as Gen Z Reshapes Market

Generation Z consumers are showing a strong preference for cold and customisable beverages over traditional hot coffee. This shift in taste is prompting major coffee chains to rethink their menus and offerings. Brands are racing to adapt their products to meet the demand for chilled, personalised drink options. The trend signals a broader generational change in how young people consume beverages at coffee retailers.

Six Dormant Bitcoin Wallets Move $40M After a Decade of Inactivity

Six Bitcoin wallets that had been untouched for ten years were activated this month, transferring approximately $40 million worth of cryptocurrency. Despite the notable movement, data from Galaxy shows that overall dormant coin activity is currently at its lowest level since 2022. The majority of funds moved from these wallets were not sent to exchanges, suggesting holders may not be looking to sell. With 2026 on track to see less than half the dormant wallet activity recorded last year, long-term holders appear largely content to keep their Bitcoin untouched.

Node.js Pattern: Use Cron as Trigger and Durable Queue for Background Jobs

A software engineering pattern recommends separating job scheduling from job execution by using a cron trigger to enqueue a small, idempotent job record, while dedicated queue workers handle the actual long-running work. The key principle is that a scheduler should only determine when a job becomes eligible, not manage its entire execution lifetime. Each scheduled occurrence is treated as a unique data record using a stable idempotency key, ensuring that duplicate trigger runs refer to the same logical job and only one execution proceeds. A lease mechanism further prevents duplicate processing by workers claiming jobs for a defined time window. The article includes a Go-based interface-driven code example to illustrate the protocol, noting the same envelope-and-claim approach applies equally to Node.js services.

Why Moving a Monitor Across a Room Cut Incident Recovery Time by 40%

A software team spent three weeks building thousands of lines of observability code to track API performance, yet users consistently detected outages before the engineering team did. A newly hired operations engineer resolved this not by writing code, but by relocating the monitoring dashboard to the customer support office, reducing mean time to recovery by 40%. The anecdote is used to argue that the tech industry's fixation on code output metrics — such as lines written or commit counts — obscures technology's core purpose: solving real problems. The author contends that equating technical skill solely with coding is a cultural and educational bias, comparable to measuring a writer's quality by typing speed. To illustrate the point further, the author describes bypassing an AI model's safety mechanisms entirely through structured natural-language dialogue, with zero lines of code written.

Why JavaScript Loops Log the Same Value and How 'let' Fixes It

A common JavaScript pitfall causes loops using setTimeout to print the same value repeatedly instead of sequential numbers. This happens because 'var' is function-scoped, meaning all iterations share a single variable that has already reached its final value by the time any callback executes. Replacing 'var' with 'let' resolves the issue, as 'let' is block-scoped and creates a fresh binding for each loop iteration. The bug is not limited to setTimeout and can appear with any deferred callback, including event listeners and promises. Understanding the scoping difference between 'var' and 'let' is key to diagnosing and preventing this entire category of bug.

Modi departs for Uzbekistan, SCO Summit

Eight-year-old boy reunites with mother after surviving Nepal floods in tree

An eight-year-old boy survived deadly floods in Nepal by climbing trees and has since been reunited with his mother. The floods have caused widespread devastation across multiple districts north of Kathmandu. According to UNICEF, at least 17,000 children have been affected by the flooding across the Rasuwa, Nuwakot, and Dhading districts. The disaster has drawn attention to the severe humanitarian impact on vulnerable young populations in the region.

How to Build Reliable Scheduled Background Jobs in Node.js Using Cron and Queues

A recommended Node.js architecture separates cron triggers from long-running background work by having the scheduler publish small, bounded tasks to a queue rather than executing full fanout processes inline. Each delivery task is represented as a durable database record containing a shipment ID, subscriber ID, event version, and a stable deduplication key to ensure retries remain safe. A unique database constraint — not an in-memory store — enforces deduplication, since process-local state is lost on restarts and can cause duplicate deliveries across multiple workers. Workers claim individual delivery records atomically, send the update to the relevant subscriber, and mark the exact version as delivered, creating a built-in audit trail for support and compliance purposes. This approach is especially critical in healthtech workflows, where a single shipment status event may fan out to dozens of subscribers and a duplicate notification could confuse patients or trigger unintended downstream actions.

Foundry & Flame: Open React Template Offers Restaurant Site With Built-In Admin Panel

A developer has released Foundry & Flame, a ready-to-use restaurant website template built with React. The template includes a customer-facing site alongside a fully functional admin panel for managing menus and editing content. It is designed to eliminate the need for hardcoding menu items or hiring a developer each time updates are needed. The project targets freelancers, agencies, and restaurant owners seeking a production-ready starting point. The developer has shared it on DEV Community and is actively seeking feedback, particularly on the admin panel's user experience.