Live data from Hacker News

The next generation of serverless

fermyon.com

1–10 of 93 posts

Re: The next generation of serverless

#4
I know I am being sold something, but this is a very convincing post IMO. I enjoyed the historical perspective, and all the mentioned downsides of serverless up until now really resonate with my own experience.

Seems like these people understand their problem space very well. Good stuff!

Re: The next generation of serverless

#5

I know I am being sold something, but this is a very convincing post IMO. I enjoyed the historical perspective, and all the mentioned downsides of serverless up until now really resonate with my own experience. Seems like these people understand their problem space very well. Good stuff!

I feel like AWS (and Lambda in this article) doesn't get enough credit for a bunch of revolutionary things they did.

Don't get me wrong, I bitch about them every day, but credit where credit is due :p

Re: The next generation of serverless

#8
I see that there's some skepticism about running WebAssembly in containers and how it constitutes a next-gen serverless solution. It's important to note that the use of WebAssembly here is not just about the runtime environment but also about the features it brings. WebAssembly binaries can start up significantly faster than traditional VMs or containers. They also have a strong isolation model and security sandbox that allows running multiple tenants in the same supervisor, which can lead to reduced costs and better utilization of resources

Re: The next generation of serverless

#9
This sales pitch ignores cloudflare workers, which sound pretty similar to me, with both webassembly and key-value storage.

The distinguishing part of the articles option seems to be that webassembly functions are uploaded in an OCI container, which I don't think anyone else supports, and I don't think was designed with this use case in mind?

Re: The next generation of serverless

#10
> Serverless apps are applications that are not written as software servers. “Server-less” code is code that responds to events (such as HTTP requests), but does not run as a daemon process listening on a socket. The networking part of serverless architectures is relegated to the infrastructure.

The networking part was always and always will be relagated to the infrastructure. Really not sold to the all "serverless" fiasco.

Post reply on HN