51–60 of 146 posts
- The function get stuck and run forever?
- It causes a request to loop?
And you have hundreds or thousands of these "functions" deployed?
Couldn't that cause sky-high costs if it goes undetected or even unwanted DDOS against other's infrastructure?
Earlier quoted context omitted.
It's less of CGI (some projects only support that) Think of it like FastCGI where most of the issues with CGI are fixed up (i.e. throughput isn't an issue) and then combine that with containerisation features from Kubernetes etc to make packaging easier (again not all projects use a Docker image format). If you're wondering whether Serverless is catching on then see also: AWS Lambda.
But isn't "serverless" fundamentally a restart-the-world model, which would make it more like CGI than FastCGI which is a application server type model which isn't fundamentally that different to putting a reverse proxy in front of a HTTP speaking application server?
Earlier quoted context omitted.
It's less of CGI (some projects only support that) Think of it like FastCGI where most of the issues with CGI are fixed up (i.e. throughput isn't an issue) and then combine that with containerisation features from Kubernetes etc to make packaging easier (again not all projects use a Docker image format). If you're wondering whether Serverless is catching on then see also: AWS Lambda.
But isn't "serverless" fundamentally a restart-the-world model, which would make it more like CGI than FastCGI which is a application server type model which isn't fundamentally that different to putting a reverse proxy in front of a HTTP speaking application server?
I'm new to serverless, but I've wondered what happens if: - The function get stuck and run forever? - It causes a request to loop? And you have hundreds or thousands of these "functions" deployed? Couldn't that cause sky-high costs if it goes undetected or even unwanted DDOS against other's infrastructure?
I'm new to serverless, but I've wondered what happens if: - The function get stuck and run forever? - It causes a request to loop? And you have hundreds or thousands of these "functions" deployed? Couldn't that cause sky-high costs if it goes undetected or even unwanted DDOS against other's infrastructure?
Since it's serverless, I assume it runs on the client. How does it scale then? And is the client really the right place to run these functions, in view of performance, and perhaps battery use?
I'm new to serverless, but I've wondered what happens if: - The function get stuck and run forever? - It causes a request to loop? And you have hundreds or thousands of these "functions" deployed? Couldn't that cause sky-high costs if it goes undetected or even unwanted DDOS against other's infrastructure?
The second is harder. Last I checked, AWS Lambda for example would allow a loop between two functions to run forever. You have to build loop detection into your software.
The cloud providers offer "serverless" billing for AWS Lambda/GCP Functions/Azure Functions in the sense that you pay just for the compute time and don't manage the underlying infrastructure.
Outside of vendor lock in, what advantage does running a service like this really offer? To make a system like this usable you'll probably need at least a couple of boxes available 24/7
Is anyone actually using this (and other open source solutions that do similar things) for anything? The cloud providers offer "serverless" billing for AWS Lambda/GCP Functions/Azure Functions in the sense that you pay just for the compute time and don't manage the underlying infrastructure. Outside of vendor lock in, what advantage does running a service like this really offer? To make a system like this usable you'…
So serverless is essentially a return to the PHP/CGI execution model... What's changed to turn a bad idea into a good idea again?