3 ms·
> much more complex to reason about and manage I really dislike the local dev experience and deployment for serverless. But otherwise the model is pretty clear
by arcturus17 6y ago
> much more complex to reason about and manage
I really dislike the local dev experience and deployment for serverless. But otherwise the model is pretty clear: a file is a function, data goes in, data comes out, just like any other server function. If one instance is busy, spin off a new one.
What’s hard to reason about?
- flak48 6y agoYep. Inversion of control has always been the norm with whatever server/framework you choose. If you have a /myroute handler defined in express or flask or even form.php or form.cgi in Apache,you never had to write the code to make user requests trigger your handler anyway even in the old days. That's the entire point of using a server instead of listening to a socket yourself With serverless the same thing still happens with someone else managing the path from a request to a handler and back. In fact, if you ever used a cpanel host with PHP like in the good old days (110mb.com anyone?), you already used 'serverless'. You just uploaded .php files to a directory and your website just 'magically' worked.