Seems pretty good on paper. There's no free allowance like you get with Workers though.
Another positive side effect would be to have paid dual redundancy then too.
Backblaze is another neighbour that plays nice with bunny.
Serverless is definitely a misnomer, but it means that you don't 'own' the server your thing is running on, there are some restrictions and you can't run anything you could on an actual VPS or hardware box. So in a way the server is abstracted away. You just use resources, but those could be anywhere, running on any node of the edge network.
Turns out, they meant installing modems in people's houses. Edge, it would seem, is a very versatile buzzword.
Serverless really should mean the client does the work, but it seems pretty equivalent to shared hosting. Dreamhost (and the shell account you used to get with an ISP!) was serverless before it was cool?
I'm aware that what they usually mean is significantly less interesting.
These days "edge" more commonly refers to the "edge of the cloud", i.e. still a datacenter, just not in us-east-1.
Serverless also does not mean no servers, it means no sysadmins.
BunnySDK.net.http.serve(async (request: Request): Response | Promise<Response> => {
return new Response("Hello World");
});
I lead Supabase Edge Functions product, a similar offering built on top of Deno runtime too. We have open-sourced our runtime (https://github.com/supabase/edge-runtime), and it's self-hostable. It supports NPM, node built-ins, pluggable storage, and web sockets. We also have a built-in API for AI inference (https://supabase.com/blog/ai-inference-now-available-in-supa...)
Supabase Edge Runtime is easy to self-host (works great as a multi-threaded JS web server). We love community contributions :) Let us know if you would like to collaborate.
Yeah, but the headache is usually from database, cache and other shared resource servers.
Scaling HTTP has been very easy for most applications for the last 15 years or so.
I have to confess I really don't see the appeal of edge workers in general outside of specific applications where latency is of high concern. Such applications do exist, of course, but this kind of offering is treated so generally that I feel like I'm either immune to the marketing or I'm missing something important.
I agree, it mostly seems like a fad/gimmick.
+ A/B testing + cookie warnings just for EU but not everyone else + proxy; helpful if you want to hide where your API is from or username/pass + route redirects + take off some workload from your server + mini applets (eg signup forms are great edge use-case)
ref: this is my old repo: https://github.com/lukeed/awesome-cloudflare-workers
* Pun intended.
I spent 2 evenings brainstorming this, but haven’t come up with anything.
Cloudflare is building an insanely good platform and I think it is one that is worth betting on into the future. I have no idea where this company came from. Maybe it's a rebrand, because they seem to have serious customer base and perhaps network footprint.
PoPs are ~119 which is significantly fewer (less than half) of Cloudflare's presence, and Cloudflare has queueing, streaming, D1 (databasing), R2, and all sorts of other things. Workers' DX cannot be beaten.
Just my 2c. If the creators are here, I'd love to know why you decided to design a new API. That is so upsetting.
If you read the article, Bunny uses Deno, CF uses a cut down version of Chromeium (each instance is like a browser tab; isolated). Thus the API difference.
But I do agree, CF is building out more of a suite.
WorkerD is open source: https://github.com/cloudflare/workerd
I personally am not a fan of Deno because of how it split the Node JS ecosystem, so that is not a benefit in my eyes. Of course, Workers can run Rust.
Nothing you said here necessitates an API difference.
I think it's pretty good, but yeah, not ideal. I'm also building a product on workers, and using D1, KV, R2, queues, and am pretty happy with the DX. Running remote previews is pretty neat.
Anyone?
As far as app logic, it depends on how much you can get the workers to do in their allotted time (which is short, iirc) so yeah, imo you still need heavier resources in a DC.
Compared to cloudflare workers, which has free bandwidth, bunnys bandwidth is not that cheap at 0.01$/GB
So while their example suggests stream-encoding video is possible, it would probably be cost-prohibitive.