Version v1.0 · dotnet

Production Guidelines

Operational guidance for stable, repeatable production deployments.

Production Guidelines

Use these guidelines to keep DurableStack workloads predictable in production.

Baseline runtime posture

  • Use a durable shared database provider for distributed workers.
  • Set a unique WorkerName per process/container.
  • Keep poll jitter enabled in multi-worker environments.
  • Keep retention enabled with explicit retention windows.

Deployment and rollout

  • Run store migrations before serving normal traffic.
  • Roll out workers gradually and monitor claim/failure trends.
  • Validate recurring schedule behavior after deployment.

Reliability practices

  • Keep handlers idempotent.
  • Use conservative max attempts for non-idempotent side effects.
  • Prefer retry backoff for unstable external dependencies.

Observability and alerting

  • Alert on failure-rate spikes and missing worker heartbeats.
  • Track retry volume and queue depth over time.
  • Validate hosted observability connectivity if enabled.