A Gentle Introduction To Restate

[@ibrahimbadr4327]

mindblowing, amazing work wallahy, you're kinda stateful guy solving stateful problems ❤ :"D

[@iislamgom3a]

Outstanding ❤

[@ahmede7141]

Perfect

[@juststudying1019]

Amazing channel thanks. greetings from syria.

[@saeedalobidi4195]

amazing 😍😍😍

[@ATesla.369]

Brilliant,Keep going

[@assaidy]

We use Arch btw😎

[@ATesla.369]

@@assaidy Oh! You got me btw 😎

[@henz103]

In the docs, did not find any mention of restate being distributed. How is it not a single point of failure?

[@asoli_dev]

This is still in the works. At the moment, if Restate is down, no workflows nor handlers will run. In the comping few months we plan on releasing the first HA version of the Runtime.

[@renatocron]

@@asoli_dev so even after HA is out, will it have any load-dist / sharding ? when compared to uber cadence for example, where each mathcing, historical, intenral worker services can run against a set of apache kafka/database, and each custom code (instance/key) can scale as long it do not exceed the number of requests per seconds that a single node can commit (including extra rouding trips, so usually very few, but's fine for most app, as events can be coalesced)