Remix.run Logo
bilalq 3 hours ago

The responses to this thread seem to be from people who are familiar with Temporal but haven't ever actually used Restate. They're both durable execution platforms, with differences mostly around how abstractions are organized and how orchestration of work happens (Temporal has you setup worker pools that pull from a queue while Restate pushes to service handlers). If some of your infra runs on serverless providers, Restate will often be a more natural fit.

Sure, Temporal is more mature and battle-tested, but Restate is quite nice and I honestly prefer it in most cases.

EDIT:

I started drafting this reply before seeing someone from the Restate team chimed in.