Загрузка видео...
Не удалось загрузить видео
We are excited to launch 𝗥𝗲𝘀𝘁𝗮𝘁𝗲 𝗕𝗬𝗢𝗖 (Bring-your-own-Cloud) today. It is fully managed restate, with all the features of Restate Cloud, but in your own account, in a dedicated VPC. Data never leaves your infra. Restate BYOC is already live in production with multiple customers, powering big workloads for... show more
202,569 просмотров • 2 месяцев назад •via X (Twitter)
Комментарии: 17

@restatedev Really proud of what the team has pulled off with BYOC 🚀 It nicely complements the existing offerings (SaaS, BYOC and on-prem) so that users can choose the deployment option that fits their needs best.

@restatedev Very excited to see BYOC finally out and can't wait to enable the advance flow control options in our latest release.

@restatedev Great job @StephanEwen and team!! So excited for this!

@restatedev congrats @StephanEwen! what did you use for the management tooling? (i strongly suggest @alien)

@restatedev @alien Yeah, @alien looks super interesting, but didn't yet exist when we started. This is currently using Nuon to handle the underlying infra, and everything above that is Restate's own stack.

@restatedev 👏👏👏

@restatedev Really cool! Also in combination with serverless functions: full setup for resilient applications with zero infra management, fully in your own cloud account.

@restatedev Congrats team 👏🚀!!!

@restatedev 🚀🚀🚀🚀🚀

@restatedev Data never leaves your infra is the line that moves regulated buyers, not the feature list. It's usually the first question in the room. Good call shipping it early.

@restatedev 所以这是连云都要自带了吗😅

@restatedev 😅

@restatedev BYOC is the deployment model of the future for all enterprises...

@restatedev data not leaving your infra is the only way enterprises actually adopt this stuff. finally

@restatedev the honest answer is that we couldn't make it work without keeping data in your control.

@restatedev congrats!!

@restatedev byoc for durable execution is underrated. keeping retries and idempotency inside your own vpc means the replay history never crosses a boundary you cant audit. the data residency angle is almost a side effect
