Why One SaaS Team Chose Cron and Queues for Recurring Reminders, Prioritizing Recovery

·3 views

A logistics SaaS developer explains a design for recurring user reminders built around a scheduler that creates durable jobs and workers that can safely retry them. Recovery was the deciding factor, since a missed reminder is minor while an unresumable payment reconciliation counts as an operational incident. The approach uses cron to wake the system, a queue to carry work, and the database to determine which reminder or reconciliation window is due. Idempotency keys are recorded before calling payment providers, transient failures are retried under a bounded policy, and persistent failures are routed to a dead-letter queue for operator review. The article compares this with a database lease for simple deployments and a managed workflow system for multi-step business processes with timers and escalations.

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)

Is the 8GB ARC A750 at $160 Worth It for Home Server Workloads?

A reader weighing a $160 8GB Intel ARC A750 GPU is assessing whether it justifies the cost for their home server. Their current Core i5 14400 relies on integrated graphics, which handles light tasks like Minecraft hosting but struggles with heavy transcoding and game streaming. The article argues the ARC A750's dedicated VRAM and parallel processing could offload Jellyfin 4K transcoding and game encoding, reducing CPU strain and stuttering. However, workloads such as NextCloud, Paperless, and Home Assistant gain nothing from a GPU, so the card's value depends on actual usage. Used NVIDIA 30-series cards at similar prices may offer better driver support and compatibility, which the analysis weighs as an alternative.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to check transparent character frames against game backgrounds before export

Transparent PNG frames can look clean on a checkerboard yet show halos or dark fringes once placed in a game scene. The article recommends testing each frame on dark, light, and scene-matched backgrounds, with attention to outlines, gaps between limbs, and small accessories. Reviewers should inspect at actual display size first, then zoom in, and check the intended camera zoom and both calm and busy backgrounds. Pixel art calls for nearest-neighbor, integer scaling, while other 2D styles should keep their intended antialiasing and be judged at the planned display scale. The piece also advises previewing the frame sequence at planned timing and testing a small sequence in the target engine to verify filtering and pivot, with a disclosure that it was prepared with an AI assistant for MotifDeck, which offers a paid download unlock.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Akamai's LKE-E clusters stuck pending after subnet IDs passed one million

Starting October 17, 2026, Akamai customers could not create new Linode Kubernetes Engine-Enterprise clusters worldwide, though existing clusters, running workloads, and scaling continued normally. Investigators traced the failure to Virtual Private Cloud subnet IDs exceeding 1,000,000, which a flaw in the Cloud Controller Manager parsed as scientific notation, making the IDs invalid. As a result, core components on new clusters stayed pending. Akamai deployed a fix enforcing strict integer formatting and patched affected resources, with the impact declared mitigated around 19:49 UTC on October 20, 2026. A postmortem update was published on October 21, 2026.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

FiftyOne Plugins Let Teams Build Custom Robot Data Curation Tools

Robot teleoperation datasets often contain flawed episodes, such as hesitations, sensor freezes, or repeated failed grasps, that are impractical to review one by one. The article argues that generic viewers cannot flag these issues because the relevant quality checks depend on each robot's hardware and data schema. It describes the FiftyOne plugin framework, which lets developers add server-side Python tools, buttons, panels, and background jobs that run across an entire dataset. Robot data differs from image data because its structure varies widely, so plugins are presented as a way to tailor checks such as motion smoothness, sensor health, and action-state alignment. Two open-source examples, lerobot_data_curation and demo_quality_scorer, demonstrate ranking LeRobot and MCAP episodes from worst to best.

0 comments Read more at DEV Community