Hacker News Reader

Sounds like inet.d, or CGI behind a webserver.

...or socket-activated systemd service [1, 2]

[1] http://0pointer.de/blog/projects/socket-activated-containers...

[2] https://developer.atlassian.com/blog/2015/03/docker-systemd-...

That's true, but for a public cloud service, you wouldn't let random people run arbitrary code based purely on inet.d or systemd socket activation.

Why not? RedHat will let you run arbitrary binaries just fine on OpenShift - both long-running/worker/"PaaS" and on-demand/per-request/"FaaS".

Obviously this is tightly locked down with cgroups.

How would you modify systemd unit files for each user of your public cloud? How would you manage the sockets once you have more users than sockets on a server?

You can create systemd units using the D-Bus API instead of files, though I'm not sure those can be socket-activated.

As for having more users than sockets, is that really likely, considering there are 64000 available ports?

Reply on news.ycombinator.com