Serverless: A lesson learned the hard way
sourcebox.be
Serverless: A lesson learned the hard way
1–10 of 139 posts
Re: Serverless: A lesson learned the hard way
#2The idea that $200 matters that much to a European programmer is so bizarre to me. I just spent that on a decent lunch for two in SF...
Re: Serverless: A lesson learned the hard way
#3"a $180 actual cost. I was left with a light headed feeling, it's a lot of money for me"
people still play with fire. limit your losses, go with digital ocean or something for 5$/mo flat no matter what.
Re: Serverless: A lesson learned the hard way
#4"The actual cost is now $206 and over $1000 forecasted, it makes me think twice about using pay-per-use services in the future."
Never use a pay-per-use service that does not include a reasonable "turn off after $X" feature and appropriate warnings. Also, never use such services without being sure to configure such settings.
I like to think of this as a self-inflicted "DDOC" attack: Distributed Denial of Capital.
Best not to leave yourself exposed.
Re: Serverless: A lesson learned the hard way
#5The idea that $200 matters that much to a European programmer is so bizarre to me. I just spent that on a decent lunch for two in SF...
I live in Florida, and even in Miami $200 is a very nice dinner once or twice a year. $200 for a decent lunch is insane.
Re: Serverless: A lesson learned the hard way
#6The idea that $200 matters that much to a European programmer is so bizarre to me. I just spent that on a decent lunch for two in SF...
[deleted]
Re: Serverless: A lesson learned the hard way
#7The idea that $200 matters that much to a European programmer is so bizarre to me. I just spent that on a decent lunch for two in SF...
That just shows you've got no idea what you're talking about
Re: Serverless: A lesson learned the hard way
#8"The actual cost is now $206 and over $1000 forecasted, it makes me think twice about using pay-per-use services in the future." Never use a pay-per-use service that does not include a reasonable "turn off after $X" feature and appropriate warnings. Also, never use such services without being sure to configure such settings. I like to think of this as a self-inflicted "DDOC" attack: Distributed Denial of Capital. Bes…
> Never use a pay-per-use service that does not include a reasonable "turn off after $X" feature and appropriate warnings.
None of the "Cloud providers" offer that. They "claim" that it could impact service - yeah, service of debt that you owe them.
Re: Serverless: A lesson learned the hard way
#9The idea that $200 matters that much to a European programmer is so bizarre to me. I just spent that on a decent lunch for two in SF...
I live in Florida, and even in Miami $200 is a very nice dinner once or twice a year. $200 for a decent lunch is insane.
He's being ridiculous. I live and work in SF. Restaurants here are definitely expensive! But my wife and I get "decent lunches" for $60, not $200. A quite nice dinner for date night is probably $120-$150. (And if we were more price-conscious, I'm pretty sure that we could get "decent" lunches and "quite nice" dinners for less than we pay).
You can of course spend much more than that if you choose. But $200 is nothing remotely close to the minimum you'd spend for a "decent lunch."
Re: Serverless: A lesson learned the hard way
#10Off topic, but the "serverless" moniker needs to die. I propose "adminless" as in "server I don't have to admin, configure, or patch" as being much more descriptive of whats really going on.