Warmup
Last updated
Sequentially loads configuration for all tenants to populate caches and avoid cold-start delays.
Reduce First-Request Latency: Pre-populates caches before real traffic arrives
Prevent Request Pile-Up: Avoids concurrent configuration loads during app startup
Improve User Experience: Ensures fast response times from the first request
Acquires an exclusive lock to prevent concurrent warmup operations
Returns HTTP 425 (Too Early) if another warmup is already in progress
Processes each tenant sequentially (not in parallel)
Continues warmup even if individual tenants fail (logs errors)
Respects cancellation tokens for graceful shutdown
Should be called by:
Azure App Service warmup triggers
Kubernetes readiness probes
Deployment scripts
Health check systems
Duration depends on number of tenants
May take several seconds to minutes for large deployments
Does not block other API requests
Warmup completed successfully.
No content
Another warmup operation is already in progress.
Unexpected server error.
No content
Last updated
GET /api/warmup HTTP/1.1
Host: app.neostore.cloud
Accept: */*