3 ms·
> Normally such announcements are coupled with an increase in per-unit price. Are there any examples of AWS ever having done this? Personally I don't recall an
by jen20 6y ago
> Normally such announcements are coupled with an increase in per-unit price.
Are there any examples of AWS ever having done this? Personally I don't recall any, but would be interested to know!
- lostcolony 6y agoYeah; citation needed. I've never seen an instance of a price increase. I can find multiple forums of people claiming Amazon has never increased prices. The only instance I can find of any cloud provider increasing prices was once in 2015 when Microsoft did in Europe...and while that led to a flurry of "cloud providers are going to increase prices" blog posts and things, calmer heads noted the exchange rates as the likely reason (and, certainly, the claims that prices would increase across the board never came to pass).
- watermelon0 6y agoI remember Google starting to charge for managed Kubernetes clusters a year or two ago, I think the cost went from 0 to 75$ per month.
- temp667 6y agoGoogle has raised prices on all sorts of things - I think AWS is one with rep for not raising prices. Maps API's I think went up pretty big time on google side.
- akiselev 6y ago> Maps API's I think went up pretty big time on google side. There were even several posts on HN around that time period of personal projects (maybe even companies) going under because of the price change.
- temp667 6y agoYeah - here's some coverage. https://geoawesomeness.com/developers-up-in-arms-over-google-maps-api-insane-price-hike/ https://geoawesomeness.com/developers-up-in-arms-over-google... That plus shutdowns of things - google is not most stable
- lostcolony 6y agoThat's fair, though I'd consider APIs to be a different beast than a cloud IaaS sort of thing. Maybe that's the distinction worth making, IaaS vs SaaS or similar. But fair point either way.
- ignoramous 6y agoAWS has admitted under-pricing S3. A new bill item, # of requests served, was added after launch. > ... When we launched S3, we were charging only for data transfer and data storage. It turned out that we had quite a few customers who were storing millions and millions of thumbnails of products they were selling on eBay. There was not much storage because these thumbnails were really small, and there wasn't much data transfer either, but there were enormous numbers of requests. It made us learn, for example, when you design interfaces, and definitely those you charge for, you want to charge for what is driving your own cost. One of the costs that we didn't anticipate was the number of requests, and request handling. We added this later to the payment model in S3, but it was clearly something we didn't anticipate. Services that came after S3 have been able to learn the lessons from S3 itself. Ref: https://m-cacm.acm.org/magazines/2021/3/250706-a-second-conversation-with-werner-vogels/fulltext https://m-cacm.acm.org/magazines/2021/3/250706-a-second-conv...