121–130 of 170 posts
Also, I can imagine clients worried about this are not the money-making kind of clients anyway.
Earlier quoted context omitted.
App Engine used to support caps. They're no longer supported, because for every customer pleasantly surprised, there were five customers incandescent with rage that their service had gone down at the worst possible moment due to a spike in actual demand.
Ho do you know? I can easily believe it, and I can easily believe that AWS employees have heard such stories, but I'd love to have it be more than an anecdote.
As a junior developer I'm always afraid using any AWS service to make a mistake that cost me a lot of money. I'm not talking about millions, simply 2k would be really bad for me.
I had been in the same position for about ten years until I set up a limited liability company. It does take some effort to set up and costs about $20/month[1], but to me the peace of mind is well worth it. [1]: https://www.ukpostbox.com/address/business-address-service
Earlier quoted context omitted.
I had been in the same position for about ten years until I set up a limited liability company. It does take some effort to set up and costs about $20/month[1], but to me the peace of mind is well worth it. [1]: https://www.ukpostbox.com/address/business-address-service
The cost to own an LLC varies a lot on jurisdiction. Even in the USA, it can vary considerably from state to state.
It's very clear why they are not doing it. Putting the risk on you instead of themselves a) is better for them for obvious reasons, and b) makes it less likely for something bad to happen in the first place. Also, I can imagine clients worried about this are not the money-making kind of clients anyway.
This is ironic in a very sad way, considering that Amazon declares customer obsession their top leadership principle [1]. [1] https://www.amazon.jobs/en/principles
How is this going to be implemented? When it reach the cap, all your service stop working? This is incredibly user hostile. If you want some warning when utilization is high, it can be relatively easy to setup with AWS's existing feature, but you need to do some configuration/tweaking on your own.
That exactly what I would like to have. Services stop and I get time to review what's happened without any stress that my bank account will be emptied.
Doesn't Google Cloud have a cap and it's completely worthless? https://dev-blog.tomilkieway.com/72k-1/
Earlier quoted context omitted.
Ho do you know? I can easily believe it, and I can easily believe that AWS employees have heard such stories, but I'd love to have it be more than an anecdote.
I could equally well believe that they got rid of it because it affected the quarterly earnings report and there was maybe one customer who was "incandescent with rage" that the caps they put in place worked exactly as advertised.
That raging customer might well assume that because almost all limits are like that, all are, including the new S3 limit, but the S3 limit causes service degradation forever, not during peak load. The writes that failed for a while map to reads that'll fail forever, because that data isn't there.
We can come up with possibilities that sound more or plausible. I'd love to hear something more factual.