My 2 cents on designing #VibeCoding ready APIs slinkydeveloper.com/blog/designi...

Webhooks that just work with @restate.dev

✅ Event persistance - let Restate acknowledge and persist the event
✅ Reliable processing - leverage Durable Execution to run until completion
✅ Idempotency - use Idempotency-Key to deduplicate

Check it out! docs.restate.dev/guides/durab...

Innovation has been completely crazy in the last few years.
Now thanks to #ClaudeCode I can finally center text in a web page!

#VibeCoding #AutoAcceptEditsAutoAcceptEdits #GPUDrivenDevelopment

🖱️Control + Alt + Restate 1.5 | Restate Restate 1.5 adds significant enhancements around observability, tools to manage function and workflow executions, and a complete documentation overhaul.

Restate 1.5 is out!

www.restate.dev/blog/announc...

Your AI Pipeline Doesn't Need a Graph, It Needs a Better Runtime You've built software systems before.

"If you need durable execution (and you probably do for production AI workflows), use a proper durable execution engine, not checkpointing as an afterthought."

This is it. Afterthought translates to time lost debugging in prod, rather than focusing on product.

StatePatching test by slinkydeveloper · Pull Request #376 · restatedev/e2e Fix #331, vibe coded while testing Junie

@intellijidea.com #Junie is wild. I asked it to write a test, using my test infra, calling an API documented only in an OpenAPI file, and it got it right first shot. Wow, the best vibe coding tool I tried so far.

github.com/restatedev/e2e/pull/376

🚀 Big news! @restate.dev 1.3 is here — and it makes handling concurrency a breeze. Complex flows? Restate journals them, making everything replayable and fault-tolerant so you can sleep easy.

Dive in 👉 restate.dev/blog/announc... to see what’s new!

Restate service handler written in Kotlin, showing how to implement a scatter/gather use case with few lines of code in a resilient way.

Coming up in @restate.dev 1.3: Implement scatter/gather scenarios with ease, while keeping your application resilient to failures! Those sub tasks can fail, the orchestrator itself can fail, and yet this code will run to completion thanks to Restate "run to completion" semantics.

Prepping my @rustikon.dev talk about @restate.dev... I'll show some use cases where you need to handle concurrent events, while keeping the application resilient from failures! #rust

The part I liked most is the second demo about email validation: it really shows how Restate gives few good high level abstractions that lets developers build concise, correct and scalable programs, which can easily deal with inherent concurrent events such as timer events and human interactions.

The simplest way to build resilient applications by Giselle van Dongen YouTube video by Jfokus

I enjoyed a lot talking at #JFokus2025 with @vdgiselle.bsky.social about @restate.dev www.youtube.com/watch?v=CADA...

🎵 Every step you take, every call you make - Restate’s fresh take on distributed apps observability Find out how the UI helps you with developing and debugging your distributed apps.

✨Restate 1.2 includes a powerful UI that lets you manage, configure, understand, and debug your applications. Restate's log contains a treasure of information to figure out what is going on in your applications. Query it now from the UI!

Learn more in the blog post 👇
restate.dev/blog/announc...

Restate 1.2: a distributed durable execution engine, built from first principles Restate 1.2 adds highly-available, distributed deployments and a graphical UI.

📢 Restate 1.2 is out! Run highly-available Restate clusters that tolerate node failures while keeping your applications responsive, and consistent. Restate now also includes a UI to give you an intuitive way to manage and debug your applications. restate.dev/blog/announc...

Looking forward to talk at #rustikonconf 🦀

Next week we will be at @jfokus.se. Come watch our talk on building resilient applications on Tuesday at 14:00 in room A4.

#JFokus2025

Every System is a Log: Avoiding coordination in distributed applications Distributed coordination makes application complex and brittle. Because all systems eventually build on logs, we can use a shared-log approach to eliminate most coordination. We discuss this conceptua...

𝐄𝐯𝐞𝐫𝐲 𝐒𝐲𝐬𝐭𝐞𝐦 𝐢𝐬 𝐚 𝐋𝐨𝐠

Here is an idea on how to drastically 𝐫𝐞𝐝𝐮𝐜𝐞 𝐜𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲 𝐚𝐧𝐝 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐢𝐨𝐧 in distributed apps.

A fun way to look at this is similar to the idea of Turning the Database Inside Out - like Turning the Microservice Inside Out.

restate.dev/blog/every-s...

👇

Distributed Restate - A first look A first look at distributed highly-available deployments of Restate and the architecture that supports those. We demonstate this through a geo-distributed active/active setup executing an order-proces...

First peek at distributed @restatedev.bsky.social: a database for durable execution.

Distributed setups scale, improve failover, and trade the dependency on persistent disk (eg EBS) with an S3 dependency. Restate replicates events internally to bridge S3's latency gap.
👇
restate.dev/blog/distrib...