News for hackers. Stuff that matters.

A comment on Serverless Architectures. Parent comment

Re:Serverless Architectures by osipov on Friday June 17, 2016 @08:47AM (#11922279)
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.
[ Parent | on HN ]
Re:Serverless Architectures by gmazza on Friday June 17, 2016 @09:00AM (#11922344)
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.

[ Parent | on HN ]
Re:Serverless Architectures by osipov on Friday June 17, 2016 @11:17AM (#11923124)
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?
[ Parent | on HN ]
Re:Serverless Architectures by icebraining on Saturday June 18, 2016 @03:28AM (#11927461)
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?

[ Parent | on HN ]