NEW
Discounted cloud compute capacity that can be interrupted or reclaimed by the provider when demand rises.
DESCRIPTION
Spot instances offer substantial discounts on compute by using spare capacity with the caveat that instances can be terminated or preempted. They suit fault-tolerant workloads like batch jobs, containerized workers, and stateless processing. Engineers design for interruptions via checkpointing, retries, and autoscaling. Each cloud provider has specific policies and pricing; AWS Spot, Azure Spot VMs, and Google Cloud Spot VMs differ in eviction signals and SLAs. Spot can drastically lower training and ETL costs when architectures are resilient.
ALTERNATIVE DEFINITIONS
AWS
Amazon EC2 Spot Instances let you take advantage of unused EC2 capacity in the AWS Cloud. Spot Instances are available at up to a 90% discount compared to On-Demand prices.
Highlights cost savings and spare capacity model.
Microsoft Learn
Azure Spot Virtual Machines provide access to unused Azure compute capacity at deep discounts. They can be evicted when Azure needs the capacity back.
Emphasizes eviction behavior and discount access to unused capacity.
Google Cloud
Spot VMs are cost-effective compute instances that can be preempted at any time. They are ideal for fault-tolerant workloads that can withstand interruptions.
Defines preemption and suitability for interruptible jobs.
RELATED TERMS
Interruptible Workloads Autoscaling Checkpointing Durability (ACID) Instance Termination Batch Processing Cost Optimization
COMPETING TERMS
On-Demand Instance Capacity Reservation Preemptible VM
KNOWLEDGE AREAS
Cloud Infrastructure Data Engineering MLOps
TARGET AUDIENCE
Cloud Architect DevOps Engineer Data Engineer MLOps Engineer AI Engineer
EXTERNAL SOURCES
- Wikipedia - Spot instance
- AWS - EC2 Spot overview and pricing
- Microsoft - Azure Spot VM documentation
- Google Cloud - GCP Spot VM docs
TOP QUESTIONS
When should Spot Instance be used?
Use Spot for fault-tolerant, stateless, or batch workloads that can handle interruptions. Training jobs with checkpointing and distributed ETL are strong candidates.
Category: Requirements
What is the biggest risk with Spot Instance?
Unexpected termination can disrupt processing. Mitigate with checkpointing, idempotent tasks, and capacity buffers or fallback to on-demand.
Category: Risks
How does Spot Instance differ across clouds?
Discounts, eviction signals, and preemption policies differ. AWS provides interruption notices; Azure offers eviction policies; GCP preempts anytime without SLA guarantees.
Category: Opinion
What are common mistakes with Spot Instance?
Running stateful services without resilience, ignoring termination signals, and failing to design retry logic can cause data loss or downtime.
Category: Mistakes
What’s an alternative to Spot Instance?
On-Demand or Reserved/Committed use provide stable capacity. Use mixed fleets or autoscaling groups with diversified allocation strategies.
Category: Alternatives
How to manage Spot Instance interruptions?
Implement checkpoints, use queues, design idempotency, monitor interruption notices, and keep fallback capacity in cheaper on-demand or reserved pools.
Category: Management
Why is Spot Instance attractive for AI training?
GPU Spot discounts can be substantial, reducing costs for large training runs. Robust checkpointing minimizes lost work during interruptions.
Category: Relevancy
How do autoscaling groups help with Spot Instance?
They replace interrupted capacity automatically, diversify instance types, and balance Spot and on-demand instances for resilience.
Category: Example
What’s a hot topic around Spot Instance?
Capacity-aware schedulers and cost-optimized multi-cloud strategies that mix Spot, on-demand, and reserved commitments are becoming standard.
Category: Topic