Ask HN: Is Serverless Good for Back End APIs?
2 comments
Hey,
At Wasmer we are working on making any traditional app serverless-like.
Basically, we can freeze and restore workloads (work in progress, not yet released publicly) very easily thanks to WebAssembly and the Wasmer runtime. Because of that, the boot time is almost non-existing.
Let me know if you would like to trial it further and I can guide through the process: https://wasmer.io/products/edge
My email: [email protected]
At Wasmer we are working on making any traditional app serverless-like.
Basically, we can freeze and restore workloads (work in progress, not yet released publicly) very easily thanks to WebAssembly and the Wasmer runtime. Because of that, the boot time is almost non-existing.
Let me know if you would like to trial it further and I can guide through the process: https://wasmer.io/products/edge
My email: [email protected]
There's also an unofficial subreddit (https://www.reddit.com/r/hetzner/), where you might be able to find more people who host their backends on one of our cloud servers, and who can give you their opinions. --Katie
I've recently been deploying my backend APIs on AWS Lambda/Cloudflare workers, and my main dislike of this method is the slow cold-boot time. I know this has been the main criticism of serverless, but I'm interested to know some of your opinions on this.
I've been thinking of ditching serverless and host my backend on a VPS on Hetzner or EC2. To anyone who has done this before, what was your experience like?