4 ms·
Their problem isn't serverless, rather Cloudflare Workers and WebAssembly. All major cloud vendors have serveless solutions based on containers, with longer ma
by pjmlp 1y ago
Their problem isn't serverless, rather Cloudflare Workers and WebAssembly.
All major cloud vendors have serveless solutions based on containers, with longer managed lifetimes between requests, and naturally the ability to use properly AOT compiled languages on the containers.
- OvervCW 1y agoAgree, it seems like they decided to use Cloudflare Workers and then fought them every step of the way instead of going back and evaluating if it actually fit the use case properly. It reminds me of the companies that start building their application using a NoSQL database and then start building their own implementation of SQL on top of it.
- zaphirplane 1y agoHey! Bet I can guess who
- CuriouslyC 1y agoIronically, I really like cloudflare but actively dislike workers and avoid them when possible. R2/KV/D1 are all fantastic and being able to shard customer data via DOs is huge, but I find myself fighting workers when I use them for non-trivial cases. Now that Cloudflare has containers I'm pushing people that way.
- keyle 1y agoYou're saying serverless can have really low latency and fast 24/7? Isn't serverless at the base the old model, of shared vms, except with a ton of people? I'm old school I guess, baremetal for days...
- pjmlp 1y agoYes, check Cloud Run, AWS Lambda, Azure Functions with containers.
- fabian2k 1y agoAt that point, why should I use serverless at all? If I have to think about the lifetime of the servers running my serverless functions?
- OvervCW 1y agoServerless only makes sense if the lifetime doesn't matter to your application, so if you find that you need to think about your lifetime then serverless is simply not the right technology for your use case.
- pjmlp 1y agoBecause it is still less management effort than taking full control of the whole infrastructure. Usually a decision factor between more serverless, or more DevOps salaries.
- fabian2k 1y agoI would doubt that this is categorically true. Serverless inherently makes the whole architecture more complex with more moving parts in most cases compared to classical web applications.
- pjmlp 1y agoDepends pretty much where those classical web applications are hosted, how big is the infrasture taking care of security, backups, scalability, failovers, and the amount of salaries being paid, including on-call bonus.
- 9rx 1y ago> Serverless inherently makes the whole architecture more complex with more moving parts Why's that? Serverless is just the generic name for CGI-like technologies, and CGI is exactly how classical web application were typically deployed historically, until Rails became such a large beast that it was too slow to continue using CGI, and thus running your application as a server to work around that problem in Rails pushed it to become the norm across the industry — at least until serverless became cool again. Making your application the server is what is more complex with more moving parts. CGI was so much simpler, albeit with the performance tradeoff. Perhaps certain implementations make things needlessly complex, but it is not clear why you think serverless must fundamentally be that way.
- CuriouslyC 1y agoCloudflare has containers now too, and having used AppRunner and Cloud Run, it's much easier to work with. Once they get rid of the container caps and add more flexibility in terms of container resources, I would never go back to the big cloud containers, the price and ease of use of Cloudflare's containers just destroy them.
- pjmlp 1y agoI doubt that the bill would be that much cheaper, nonetheless thanks for making me aware they are a thing now.
- CuriouslyC 1y agoThey're much cheaper, they're just DOs, and they get billed as such. They also have faster cold start times and automatic multi-region support.
- OvervCW 1y agoWhat does DO mean in this context?
- CuriouslyC 1y agoDurable Object
- iainmerrick 1y agoIn that scenario, how do you keep cold startup as fast as possible? The nice thing about JS workers is that they can start really fast from cold. If you have low or irregular load, but latency is important, Cloudflare Workers or equivalent is a great solution (as the article says towards the end). If you really need a full-featured container with AOT compiled code, won't that almost certainly have a longer cold startup time? In that scenario, surely you're better off with a dedicated server to minimise latency (assuming you care about latency). But then you lose the ability to scale down to zero, which is the key advantage of serverless.
- pjmlp 1y agoApparently not nice enough, given that they rewrote the application in Go. Serverless with containers is basically managed Kubernetes, where someone else has the headache to keep the whole infrastructure running.
- Quarrel 1y agoIndeed. They get to the bottom of the post and drop: > Fargate handles scaling for us without the serverless constraints They dropped workers for containers.