Urgent.News

What's breaking now, across thousands of outlets.

Tech

Polling Before Webhooks for Auditable SMS Delivery Records in Node.js Logistics Systems

A logistics compliance notice needs a delivery record that survives the process that sent it. That constraint changes an SMS API comparison: a convenient send call contributes little if the application cannot later explain which notice it submitted, which status it observed, and what evidence remains missing. Start with the record. Short answer: choose polling first for a Node.js logistics…

Node.js logistics systems demand an auditable SMS delivery record to satisfy compliance requirements. This necessitates polling before webhooks for establishing an evidence trail. The record must include information about the intent to send, acceptance by the external service, and subsequent delivery evidence observed by the application.

A single mutable status field is insufficient to explain complex scenarios like operator corrections or retries. Instead, assign an internal notice identifier, associate it with the notice text and intended destination, and persist the submission outcome separately from observations. The external message identifier should be retained when available, along with sufficient adapter context to interpret it later.

Corrections should result in new notice attempts linked to the original intent to avoid confusion. The distinction between observations and conclusions is crucial; store the external status as observed, the time received, and any external event time if provided. Derive the application's conclusions from these records using a documented mapping.

Uncertainty should be queryable, allowing for reconciliation work without silently asserting success or triggering another SMS. The integration design should be based on the evidence boundary. Polling involves selecting outstanding notice attempts, retrieving status through an adapter, recording the observation durably, and scheduling further checks according to policy.

Webhooks move the receiving boundary into the application, requiring authentication, storage of observations, and acknowledgment only after a durable handoff succeeds. Establish the actual rules for retries, event identifiers, ordering, and replay before deployment. This record design, independent of the programming language, models observations rather than network clients.

The provided Python example illustrates the concept, emphasizing the importance of preserving raw observations for later mapping changes and retention obligations. Comparing polling and webhooks reveals that existing infrastructure may favor polling if a durable scheduled worker is available, while webhooks are suitable when an authenticated public receiver is present and faster delivery is required. The choice depends on existing infrastructure and timing requirements.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Keeping Sitemap Lastmod Dates Honest on a Law Firm Site

Most CMS platforms and sitemap plugins fill in the lastmod field automatically. Some use the date of the last database save.

  • Accurate lastmod dates are crucial for search engines like Google.
  • Only significant content changes should trigger lastmod updates.
  • Documenting the rule for developers and editors ensures compliance.

The SVG Was Already Broken. Did the Agent Make It Worse?

Search was already missing from our SVG toolbar. Print worked. We asked Codex to make one change: turn the green status light orange. The saved SVG still had one broken reference. Was it the same one?

  • SVG toolbar missing search button.
  • Print function unchanged after recoloring.
  • One broken reference remained after change.

Is AWS Blocks Becoming "CDK Blocks"? What the Move to aws/cdk-blocks and the Rename Change

When I opened the AWS Blocks repository this morning (Japan time), the URL had changed. aws/cdk-blocks on GitHub I have been contributing to aws-devtools-labs/aws-blocks since the public preview…

  • AWS Blocks repository moved from aws-devtools-labs to aws organization on Nov 18, 2026.
  • Renamed to CDK Blocks on Nov 17, 2026, at 11:18 PM UTC.
  • Transfer suggests AWS Blocks integration with CDK family.

More from Wednesday 18 November →