[syrusakbary]

Here are some of the thoughts behind my reasoning that I posted previously in HN. Hope the are insightful!

https://news.ycombinator.com/item?id=27158187

https://news.ycombinator.com/item?id=26271806

[vlunkr]

Even if you change the unit of computation in k8s from a container, that's only one problem that it solves. What about deployments, services, ingress, configmaps/secrets, jobs, volumes, etc. If you're going to create your own distributed system, all these concepts are going to exist in some form.

[_mme]

Thanks, this is interesting, but also very abstract.

What do you mean when you say "scaling on the level of a function"?

Do you mean any "plain old" function or a specific REST endpoint like AWS Lambda?

If you could just throw distributed computing resources at any function that is a bottleneck in your code, that would be alien tech.

[CMCDragonkai]

It means going in certain directions.

Going from coarse-grained compute to fine-grained compute. The finer grain you have, the more "composability" and "flexibility" you get.

At some point you become so fine-grain that all you have are just lambdas floating in the cloud. And universal pointers to data floating in the cloud. Wire them up and everything scales automatically.

Back when I was working on this sort of stuff, there was an intermediate development between containers and wasm, that being of library OS like mirage OS, unikernels... Etc. I think wasm has probably better positioning compared to those unikernels.

[_mme]

So it's a satire?