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.

Exploring @restate.dev as a replacement for some long-running, complex, asynchronous orchestrators currently implemented in Step Functions. This 2023 post resonates hard. Lambda chain -> Step Functions is an increasingly common migration but comes up short vs RPC/ECS restate.dev/blog/we-repl...

Wow, what a blast from the past. Thank you for bringing that back 🙂 This is from a talk "All roads lead to Rome" - hence the helmets.

Is this where we currently are?

Restate is one of the coolest pieces of software I've encountered in quite awhile. Not often a tiny, well-crafted application comes along that forces you to fundamentally rethink software design.

This post from @stephanewen.bsky.social is *really* thought provoking. Their architecture seems to unify both database and stream processing architecture into one thing. I'm not totally sure what the implications of this are yet, but it seems important.

It’s really impressive! I almost went down the path of building a stateful functions implementation in Rust but discovered how much scaffolding was required to be useful. Really happy to see you all have put those pieces together with Restate!

Restate is much simpler than Flink, however, grasping what it does isn't straight forward given how differently it works. This tutorial is fantastic and worth the time:

Regarding Restate and its distributed log, many people talk about Delos but Apache BookKeeper is also highly relevant/similar, so I like to remind people that it also exists! I've written extensively about how BookKeeper works if you're interested: 1\ medium.com/splunk-maas/...

Great stuff. I'm watching the durable execution space closely and personally I'm quite bullish on it. I'll be writing my own thoughts on durable execution soon.

𝐄𝐯𝐞𝐫𝐲 𝐒𝐲𝐬𝐭𝐞𝐦 𝐢𝐬 𝐚 𝐋𝐨𝐠 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... 👇

𝐄𝐯𝐞𝐫𝐲 𝐒𝐲𝐬𝐭𝐞𝐦 𝐢𝐬 𝐚 𝐋𝐨𝐠 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... 👇

This is why we are building software and open-source communities. To get such messages from users, the best possible reward. Kudos to the entire @restatedev.bsky.social team.

My first post on @bsky.app - let's go!

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...

The unofficial GIF-based pandas library documentation. pandas.DataFrame.rolling