{
  "id": 17839440,
  "title": "Surviving AWS Spot Interruptions With Real Checkpointing",
  "url": "https://urgent.news/2026/11/02/surviving-aws-spot-interruptions-with-real-checkpointing",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-02T19:04:40.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/renato_silva_71eef0fc385f/surviving-aws-spot-interruptions-with-real-checkpointing-1o31"
  },
  "original_language": "en",
  "account": "Spot instances are significantly cheaper than on-demand options, but they come with the risk of interruption. Most teams find out their workloads are not truly fault-tolerant until it's too late. Restarting from scratch after an interruption can be costly and inefficient, especially for long-running jobs. The key to mitigating these interruptions is implementing a checkpointing pattern. This pattern involves three components: a checkpoint writer that serializes progress to durable storage, a progress ledger to track what has been checkpointed, and an interruption watcher that triggers an emergency checkpoint upon receiving a termination notice. The interruption watcher polls AWS's metadata service, which provides a termination notice roughly two minutes before reclamation. This gives enough time to save minimal state and exit cleanly. The checkpoint cadence should be set to balance the trade-off between minimizing I/O overhead and maximizing replay cost. A formula, checkpoint_interval ≈ sqrt(2 * checkpoint_write_cost / interruption_rate), has proven effective. For queue workers, checkpointing per message batch can be an effective alternative. By implementing this checkpointing pattern, you can make spot interruptions a non-event, ensuring your workloads remain resilient and cost-effective.",
  "summary": "🔧 The Problem Spot instances are 60-90% cheaper than on-demand, and the pitch is always the same: \"just make your workload fault-tolerant.\" Great, thanks. In practice, most teams discover their batch job, training run, or queue worker isn't actually fault-tolerant until the first 3am page from a spot reclamation mid-run. The naive fix is restarting the job from scratch after interruption. For a…",
  "key_points": [
    "Implement checkpointing pattern to mitigate spot interruptions",
    "Checkpoint writer serializes progress to durable storage",
    "Interruption watcher triggers emergency checkpoint on termination notice"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}