Server Deployment And Registration

An operator deploys a new SDK service (HTTP endpoint) but never registers it with the Restate Server, then is surprised the server cannot route to it.

Register the deployment with the Restate Server (restate CLI / admin API deployment registration pointing at the service endpoint URL) so the server discovers its services/handlers and can route invocations. Registration is the discovery step — code running is not enough. Re-register (or use the do…

A team builds half their services with the TypeScript SDK and half with the Java SDK and assumes every primitive behaves identically across both.

Restate provides multiple SDKs (e.g. TypeScript, Java/Kotlin, Python, Go, Rust) that share the same durable-execution model, but verify per-SDK API names and feature parity for the primitives you use (ctx.run, awakeables, virtual objects) against each SDK's docs rather than assuming identical surfa…

An operator deploys Restate handlers as AWS Lambda functions and assumes a blocking 30-minute ctx.sleep keeps the Lambda warm and billing for the whole wait.

On a serverless deployment, a durable wait suspends the invocation and the function returns; Restate re-invokes the function to resume after the wait — so you are not billed for idle wait time and you do not need the function alive throughout. Design handlers to be resumable across separate functio…