5 ms·
I was really hoping they would post at least a preview of what the pricing will be. AppEngine pricing change resulted in a nasty surprise for a lot of people a
by sologoub 11y ago
I was really hoping they would post at least a preview of what the pricing will be.
AppEngine pricing change resulted in a nasty surprise for a lot of people and a lot of vitriol towards Google. Just one article on this from many: http://readwrite.com/2011/09/02/google-app-engine-pricing-ange/ http://readwrite.com/2011/09/02/google-app-engine-pricing-an...
While the platform has moved way ahead of where it was in 2011, the memory of this is still in the back of people's mind and it would be a good move on Google's part to at least try to engender more trust by giving directional pricing.
- mianos 11y agoIt is funny reading this in hindsight. We went straight to AWS, also for long running tcp connections, and never looked at it again. After that I have never recommended app engine.
- bduerst 11y agoWasn't that five years ago? When it came out of preview (and prices were expected to change)?
- sologoub 11y agoIt was - 2011 is mentioned in both article and my comment. I just wish Google wouldn't bring back memories of that by not disclosing pricing of a very promising API. GAE has moved quite far ahead since then, but many people still won't consider it after the bad experience. Perceptions die hard...
- deleted 11y ago[deleted]
- dragonwriter 11y agoThey probably are using usage data in the free period to drive decisions on pricing.
- sologoub 11y agoSure, would expect nothing less, but I'm also sure they have some sense of the range they are looking for. Such a range could help developers to establish whether their use case is viable or not. As is, the ambiguity is a deterrent from too much time investment.
- bduerst 11y agoOr the data determines that they have to price outside the hypothetical early-release range, and then you have people complaining that you lied.