Top all-time · #2963
Restate
Company blog · restate.dev/blogsystemsprogrammingai
Restate is the company blog at restate.dev, writing about systems, programming and ai. Since 2023, 24 different Hacker News readers have linked it 73 times, most often “Restate: innately resilient backends and agents”. No feed was found, so read it on the site itself.
Too few sampled comments (19) to say how often HN recommends it.?
Why HN links it
HN readers link Restate's blog for durable execution and workflows, notably the 'every system is a log' post and the post on why Restate was built. Mostly cited as product references; one commenter calls a post excellent.
Summarised by Claude from a sample of 19 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Restate is a low-latency application runtime with durable execution, keyed state, queues, RPC, timers, flow control, and operational control in one binary.
Most-linked posts?
- Restate: innately resilient backends and agents5 people · 5 mentions · first linked 2023-09-28
- Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust4 people · 4 mentions · first linked 2024-06-12
- Code that sleeps for a month: Solving durable execution's immutability problem3 people · 4 mentions · first linked 2024-02-23
- Every System is a Log: Avoiding coordination in distributed applications3 people · 3 mentions · first linked 2025-01-24
- How to keep your apps up when AWS is down2 people · 3 mentions · first linked 2025-10-21
- Remote Control for Agents2 people · 3 mentions · first linked 2026-02-17
- Making Durable Agents2 people · 3 mentions · first linked 2025-10-21
- Restate 1.3: Concurrency without losing sleep2 people · 3 mentions · first linked 2025-04-10
- We built Restate. Resilient applications using distributed durable async/await2 people · 2 mentions · first linked 2023-08-30
- /2 people · 2 mentions · first linked 2024-10-06
What Hacker News says?
Yes, there is one, have a look at https://restate.dev/cloud/
Comment linking /cloud/
on “Every System is a Log: Avoiding coordination in distributed applications”Submitted Every System is a Log: Avoiding coordination in distributed applications as a story · 229 points
HN discussionrelatedly: https://restate.dev/blog/every-system-is-a-log-avoiding-coor... https://news.ycombinator.com/item?id=42813049
Comment linking /blog/every-system-is-a-log-avoiding-coordination-in-distributed-applications/
on “Turning the database inside-out (2015)”Submitted Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust as a story · 185 points
HN discussionI hope @sewen will expand on this but from the blog post he wrote to announce Restate to the world back in August '23: > Stateful Functions (in Apache Flink): Our thoughts started a while back, and our early experiments created StateFun. These thoughts and ideas then grew to be much much more now, resulting in Restate. Of course, you can still recognize some of the StateFun roots in Restate. The full post is at: htt…
Comment linking /blog/why-we-built-restate/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted Building a modern durable execution engine from first principles as a story · 98 points
HN discussionYeah, this is pretty much exactly how we propose its done (restate services are inherently versioned, you can register new code as a new version and old invocations will go to the old version). The only caveat being that we generally recommend that you keep it to just a few minutes, and use delayed calls and our state primitives to have effects that span longer than that. Eg, to poll repeatedly a handler can delayed…
Comment linking /blog/code-that-sleeps-for-a-month/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted Solving durable execution's immutability problem as a story · 52 points
HN discussionA few links worth sharing here: - Blog post with an overview of Restate 1.0: https://restate.dev/blog/announcing-restate-1.0-restate-clou... - Restate docs: https://docs.restate.dev/ - Discord, for anyone who wants to chat interactively: https://discord.com/invite/skW3AZ6uGd
Comment linking /blog/announcing-restate-1.0-restate-cloud-and-our-seed-funding-round/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted From Prompt to Adventures:Creating Games with LLMs and Restate Durable Functions as a story · 49 points
HN discussionI wrote two blog posts on this! It's a really hard problem https://restate.dev/blog/solving-durable-executions-immutabi... https://restate.dev/blog/code-that-sleeps-for-a-month/ The key takeaways: 1. Immutable code platforms (like Lambda) make things much more tractable - old code being executable for 'as long as your handlers run' is the property you need. This can also be achieved in Kubernetes with some clever co…
Comment linking /blog/code-that-sleeps-for-a-month/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted The Anatomy of a Durable Execution Stack from First Principles as a story · 22 points
HN discussionwe talk a bit about compensations in the post: https://restate.dev/blog/graceful-cancellations-how-to-keep-... the gist is that you can just use catch statements and put rollback logic in it. Restate guarantees that handlers run to the end, so there's no risk that it somehow won't reach the catch statement due to an infra failure. So catch, rethrow, and then all the way up the stack, the compensations will run
Comment linking /blog/graceful-cancellations-how-to-keep-your-application-and-workflow-state-consistent/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted Code that sleeps for a month: Solving durable execution's immutability problem as a story · 13 points
HN discussionHey all, I work with @sewen, and I focus on the cloud platform which also launched today ( https://restate.dev/blog/announcing-restate-cloud-early-acce... ) Happy to answer any questions :)
Comment linking /blog/announcing-restate-cloud-early-access/
on “Show HN: Restate – Low-latency durable workflows for JavaScript/Java, in Rust”Submitted Building a distributed database for durable execution as a story · 10 points
HN discussionMy sentiments exactly - well said. The big mistake is forcing OOP onto everything. It's why I really have an affinity with the virtual actor, it has just enough OOP for me to have classes, methods and internal state - I don't need inheritance, polymorphism, etc - just naive little classifications of things we call objects. I also don't have to think of my system in a hierarchical supervised manner like earlier actor…
Comment linking /
on “Thinking in Actors – Challenging your software modelling to be simpler”Submitted How to keep your apps up when AWS is down as a story · 6 points
HN discussionWhile this does talk about durable queues , this post really hinges on a pivot to evangelizing durable workflows . It makes it sound like they're synonymous, when they're very much not. Specifically, this sentence bringing up workflows for the first time (emphasis mine): > "Durable queues were rare when I was at Reddit, but they’re more and more popular now. Essentially, they work by combining task queues with durab…
Comment linking /
on “I solved a distributed queue problem after 15 years”Submitted Building an LLM Chat and Task Bot with Durable Execution as a story · 6 points
HN discussionIt's also similar to https://www.restate.dev/ .
Comment linking /
on “Make any TypeScript function durable”Submitted Every step you take, every call you make: distributed apps observability as a story · 5 points
HN discussionThey mention it in their about page: https://restate.dev/about
Comment linking /about
on “Building a modern durable execution engine from first principles”Submitted We got 400 LoC StepFunctions to 40 LoC TypeScript by making Lambdas suspendable as a story · 5 points
HN discussionThis is also a good use case for durable execution, see eg https://restate.dev
Comment linking /
on “Distributed transactions in Go: Read before you try”Submitted Building stateful serverless applications with Knative and Restate as a story · 4 points
HN discussionSorry, but this is incorrect (Restate founder here) (1) You can model the equivalent of local activities and activities that run on other workers in Restate. A local activity is a step in the workflow function. An activity supposed to run on a different worker is a function called by the workflow function. Since these calls are just Restate events, exactly-one, suspendable, this gives you a full-fledged workflow/rem…
Comment linking /blog/announcing-restate-1-7
on “Temporal raises $550M at a $12.55B valuation”Submitted Restate 1.3: Concurrency without losing sleep as a story · 4 points
HN discussionDisclaimer: 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-maste... ) 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 Re…
Comment linking /vs/temporal
on “Temporal raises $550M at a $12.55B valuation”Submitted Release announcement: Restate 0.8 has arrived as a story · 4 points
HN discussion
