3 ms·
How is no spending limit a serverless problem? It's a cloud problem. Edit: Well, if you have small cloud servers they might go down under an attack. And if yo
by usr1106 3y ago
How is no spending limit a serverless problem?
It's a cloud problem.
Edit: Well, if you have small cloud servers they might go down under an attack. And if you pay only outgoing like in AWS that's good for you.
- simonjgreen 3y agoIt’s an architecture failing. Setting maximums is critical. If you choose a platform that doesn’t support that more fool you. It’s implicitly easier to have a ‘circuit breaker’ in a traditional environment, but still warrants consideration. Load test for success and failure.
- happymellon 3y agoIt's not a cloud problem. The cloud is just somebody else's computer. It's either a billing or an architecture problem. Either let me throttle requests to prevent overbilling, or cut me off when I hit a certain value.
- Hamuko 3y agoBecause serverless 1) uses pay-as-you-go more often than traditional models 2) scales better to achieve massive usage. If you DDoS my $5/month DigitalOcean VPS, it's not going to increase how much I have to pay DigitalOcean in terms of compute, and most likely the VPS will buckle under load before it can actually rack up massive transfer costs (since those are also pay-as-you-go for DO).
- lelanthran 3y ago> How is no spending limit a serverless problem? > It's a cloud problem. It's a serverless problem because it can be mitigated if using the cloud, but not mitigated if it is serverless. I have a cloud instance. I don't have this problem and never will. If I had serverless instead, I will have this problem.