4 ms·
In what potential world would it ever make sense to start an entire container for each request? The entire architecture that leads to such a concept is so dumb
by fake-name 5y ago
In what potential world would it ever make sense to start an entire container for each request?
The entire architecture that leads to such a concept is so dumb I have trouble believing anyone ever thought it could be a decent idea.
- tiffanyh 5y agoThats how Erlang works essentially.
- foepys 5y agoYes but Erlang's BEAM as a purposely built architecture that makes this very efficient. Spawning OS processes and threads is comparatively expensive.
- nesarkvechnep 5y agoErlang doesn’t spawn containers for every request.
- lmeyerov 5y agoExtreme take: Numbers-wise, that should probably be the default ;-) In particular, the world runs on power laws, and I'm betting most server apps are boring occasional internal stuff at the not-even-1-qps level. Long tails add up to be the typical project. So yeah, if all the worlds internal django tools can do scale-to-zero with fast cold start on shared boxes with 100X more tenancy than today, that's saving a lot of electricity & hw. Sort of a virtualization equivalent of "640K ought to be enough for anybody".
- tyingq 5y ago>In what potential world would it ever make sense to start an entire container for each request? If you wait long enough between requests (~5 minutes), that is what AWS Lambda does, only with a VM instead of a container.