3 ms·
But you forgot that always-on server it lives on. The idea behind serverless includes the fact that you don't pay for what you don't use. So if no requests are
by qayxc 6y ago
But you forgot that always-on server it lives on.
The idea behind serverless includes the fact that you don't pay for what you don't use. So if no requests are served, you owe nothing.
Your FCGI solution shuts down idle copies, but keeps the server running...
- recursive 6y agoI don't really understand serverless, but if it's running a process in response to a request, then of course there's still a server, because something received that request. FCGI has a server running. And serverless has a server running, as long as its listening for requests.
- jacobsenscott 6y agoThe running server is a server you don't pay for.
- recursive 6y agoSo the truth is revealed. The real technology of serverless is an innovation in billing models.
- codyb 6y agoServerless architectures rely on some sort of gateway run by their cloud provider as their always on listener which spins up a process for your function when needed. Essentially it’s a collective pooling which is cheap enough that it can be offered for “free” to the entity creating a serverless workflow.
- gitgud 6y ago> But you forgot that always-on server it lives on. A better comparison would be "Serverless" is "FCGI in shared environment"... if such a thing exists...
- recursive 6y agoI recall running perl and php on shared hosts in the 90s. Probably not FCGI, but probably close in spirit.
- Animats 6y agoThat's still available from many hosting providers. It's very cheap. I run Go programs that way on Dreamhost. You're not stuck in the Perl era. I compile the executables on a Linux desktop and push them to the server. Costs under US$10/month. You can probably do 10-100 transactions per second.