Wanted to try Amp's self-hosted orbs, and built a integration to run on you @cloudflare workers.
Looking for testers! @mrnugget @paulinevos @robelsust
Each orb is a Container, one per Amp thread. A Worker with Durable Objects starts and pauses them. Paused orbs snapshot to…
Commit
7910bcf
Awesome work @meirdick. Bringing Orbs over to CF Workers with cf-orbs init makes so much sense for keep-alive latency and zero-cost idle state.
Happy to help test. How are you handling the memory footprint when Workers snapshot/resume those Container threads, any weird cold…
no memory snapshots, but snapshot the disk. This is how many of the other self hosted providers do it when memory snapshots are not possible.
Resume is a clean spawn from disk in 2.3 s, so there's no resume spike to manage. Extensively tested and soak tested with higher reliability then the vercel and e2B. - a little more info here https://cf-orbs-site.mdick85.workers.dev/
cf-orbs-site.mdick85.workers.devcf-orbs: Amp orbs, on machines you ownSelf-hosted Amp orbs on your own Cloudflare account. Open source, Apache-2.0.
commit 7910bcf