{"slug": "restate", "name": "Restate", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 2, "commenters": 4, "warners": 0, "score": 2.113, "rising": -0.65, "first": "2025-11-14", "latest": "2026-08-06", "why": "Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 2, "neutral": 0, "compare": 2, "warn": 0}, "spark": [0, 0, 0, 0, 1, 0, 1, 0, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free", "icon": false, "domain": "restate.dev", "github_repo": null, "official_url": "https://restate.dev", "pricing": "", "aliases": ["Restate"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 773046400, "item_id": 48315400, "url": "https://news.ycombinator.com/item?id=48315400", "by": "saxenaabhi", "date": "2026-05-28", "stance": "recommend", "quote": "Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free", "excerpt": "As someone who uses dbos.dev, restate.dev, cf workflows here is a snippet from our Agents.md We use durable execution a lot since we are handling payments/orders. For durable execution right now we are using - 1. **Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free, - 2. **Cloudflare workflows** for non crit", "context": "handles payments/orders", "use_case": "durable execution for payments", "switched_from": "", "story": "Just Use Postgres for Durable Workflows"}, {"id": 755483696, "item_id": 47217731, "url": "https://news.ycombinator.com/item?id=47217731", "by": "erdaniels", "date": "2026-03-02", "stance": "recommend", "quote": "We chose this internally after evaluating it against temporal, hatchet, and dbos.", "excerpt": "Also check out https://www.restate.dev/. We chose this internally after evaluating it against temporal, hatchet, and dbos. The docs are pretty good and development locally and deployment to k8s was simple.", "context": "", "use_case": "durable execution", "switched_from": "", "story": "Go-Native Durable Execution"}]}], "caveats": [], "who": [{"by": "saxenaabhi", "context": "handles payments/orders", "url": "https://news.ycombinator.com/item?id=48315400", "date": "2026-05-28"}], "tags": [], "use_cases": ["durable execution", "durable execution for payments", "durable workflows"], "compared": [{"slug": "temporal", "name": "Temporal", "co": 5, "switched_from": 0, "switched_to": 0}, {"slug": "dbos", "name": "DBOS", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "cloudflare-workflows", "name": "Cloudflare Workflows", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 795174736, "item_id": 49698421, "url": "https://news.ycombinator.com/item?id=49698421", "by": "stsffap", "date": "2026-09-14", "stance": "recommend", "quote": "Disclaimer: I am a co-founder of Restate and might be biased.", "excerpt": "Disclaimer: I am a co-founder of Restate and might be biased. Restate's spiritual father is Stateful Functions (https://nightlies.apache.org/flink/flink-statefun-docs-master/) a library for event driven applications built on top of Apache Flink. If you want to learn more about why we started building Restate, I recommend this excellent blog post https://restate.dev/blog/why-we-built-restate. I understand that Restate", "context": "co-founder of Restate", "use_case": "durable execution runtime", "switched_from": "", "story": "Temporal raises $550M at a $12.55B valuation"}], "threads": [{"url": "https://news.ycombinator.com/item?id=49696335", "title": "Temporal raises $550M at a $12.55B valuation", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49185430", "title": "Celld: Self-hosted, distributed Durable Objects", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48313530", "title": "Just Use Postgres for Durable Workflows", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47160065", "title": "Go-Native Durable Execution", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=45920156", "title": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows", "mentions": 1}], "sentiment_by_month": {"2025-11": {"compare": 1}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {"recommend": 1}, "2026-04": {}, "2026-05": {"recommend": 1}, "2026-06": {}, "2026-07": {}, "2026-08": {"compare": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 787117441, "item_id": 49194840, "url": "https://news.ycombinator.com/item?id=49194840", "by": "7bit", "date": "2026-08-06", "stance": "compare", "quote": "is this something that compares to Temporal or Restate or Azure Durable Functions?", "excerpt": "Hey, is this something that compares to Temporal or Restate or Azure Durable Functions? If so, what are the differences and when would I use Cells instead of the aforementioned?", "context": "", "use_case": "durable execution", "switched_from": "", "story": "Celld: Self-hosted, distributed Durable Objects"}, {"id": 773046400, "item_id": 48315400, "url": "https://news.ycombinator.com/item?id=48315400", "by": "saxenaabhi", "date": "2026-05-28", "stance": "recommend", "quote": "Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free", "excerpt": "As someone who uses dbos.dev, restate.dev, cf workflows here is a snippet from our Agents.md We use durable execution a lot since we are handling payments/orders. For durable execution right now we are using - 1. **Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free, - 2. **Cloudflare workflows** for non crit", "context": "handles payments/orders", "use_case": "durable execution for payments", "switched_from": "", "story": "Just Use Postgres for Durable Workflows"}, {"id": 755483696, "item_id": 47217731, "url": "https://news.ycombinator.com/item?id=47217731", "by": "erdaniels", "date": "2026-03-02", "stance": "recommend", "quote": "We chose this internally after evaluating it against temporal, hatchet, and dbos.", "excerpt": "Also check out https://www.restate.dev/. We chose this internally after evaluating it against temporal, hatchet, and dbos. The docs are pretty good and development locally and deployment to k8s was simple.", "context": "", "use_case": "durable execution", "switched_from": "", "story": "Go-Native Durable Execution"}, {"id": 734843473, "item_id": 45927717, "url": "https://news.ycombinator.com/item?id=45927717", "by": "KraftyOne", "date": "2025-11-14", "stance": "compare", "quote": "you have to operate that orchestrator and its data store in production (and it's a single point of failure)", "excerpt": "The Restate model depends on a long-running external orchestrator to do the \"pushing\". However, that comes with downsides--you have to operate that orchestrator and its data store in production (and it's a single point of failure) and you have to rearchitect your application around it. DBOS implements a simpler library-based architecture where each of your processes independently \"pulls\" from a database queue. To mak", "context": "", "use_case": "durable workflows", "switched_from": "", "story": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows"}]}