4 ms·
The concept of “serverless” is just based around trying to recreate a cgi from a long-running process application. Like you pointed out, we have had this since
by samtho 3y ago
The concept of “serverless” is just based around trying to recreate a cgi from a long-running process application. Like you pointed out, we have had this since mod_php.
- MrBuddyCasino 3y agoExcept we didn’t have spend a day to get the IAM permissions just right and embed some javascript into a huge blob of YAML. Simpler times.
- biorach 3y agoAlso, less secure times
- samtho 3y agoMaybe in general, but that does not encompass every project or organization utilizing web technologies. There was technical know-how but often just a lack of willingness or understanding from higher up that prevented a security-focused approach to building applications.
- fauigerzigerk 3y agoServerless is CGI for dynamically allocated server clusters managed by other people. We didn't have that.
- samtho 3y agoFrom the user’s point of view (someone developing an application), we did via shared hosting and cgi-style scripting. It doesn’t really matter what tech powered the infrastructure as long as it worked. Putting PHP scripts on in a folder to be called at will to perform specific actions was a pattern utilized to great effect with the additional benefit of not having to wait for the function to spin up.
- nailer 3y agoWasn’t the creation of mod_ the ability to keep the interpreter open? Yes, before that, we had stateless scripting in web apps. Like serverless it was far easier to debug. Unlike serverless it was slow.