congrats all! this is a huge step, especially all the intangibles like the new SLA and infrastructure changes that are really critical but easy to overlook. fingers crossed for the rollout!
I love GAE and have built several solutions for clients on it. Luckily I don't have to worry about them dropping support for it like they did with Buzz ,Wave, etc..
All of my GAE apps are built with web2py which allows me to take the exact same code and run it on any system I wish as long as it has Python >2.4. So if Google decides to shutdown GAE tomorrow I could have all of my clients back up and running on AWS or RackSpace or even DreamHost in a matter of hours.
As we all know, Google pissed a lot of people off by changing the way GAE bills apps (by instance hours, a la Amazon's EC2, instead of CPU use as was originally the case for App Engine). As a result, many people are paying on the order of 10x what they originally did.
I just looked at the free quotas, and they seem pretty generous to me. Who's going over 46 million XMPP calls _per day_? I suppose it's probably the 1GB of daily bandwidth in each direction that people go way over? Or the 100 mails/day? All other quotas seems difficult to surpass.
Admittedly I'd totally bought into the "App Engine sucks" rhetoric, but if you're using that much of Google's resources, shouldn't you be paying them?
That said, I personally know people who have relatively low-traffic GAE apps deployed and who will supposedly be taking them down soon due to cost.
Are they forgetting about the free quota or what? What am I missing???
@snarfed.org you seem to work for google... no surprise that you are happy with "all the intangibles like the new SLA and infrastructure changes" .. ha ha they are too intangible .. I can bet that SSL support and the old price scheme would be much more appreciated than these intangible things... let's hope google will add some tangible features in the next release !
When will Python 2.7 support come out of its "experimental" designation?
ReplyDeletecongrats all! this is a huge step, especially all the intangibles like the new SLA and infrastructure changes that are really critical but easy to overlook. fingers crossed for the rollout!
ReplyDeleteI love GAE and have built several solutions for clients on it. Luckily I don't have to worry about them dropping support for it like they did with Buzz ,Wave, etc..
ReplyDeleteAll of my GAE apps are built with web2py which allows me to take the exact same code and run it on any system I wish as long as it has Python >2.4. So if Google decides to shutdown GAE tomorrow I could have all of my clients back up and running on AWS or RackSpace or even DreamHost in a matter of hours.
निःशुल्क ज्योतिष सेवा रात्रि ८ से९ ऑनलाइन या फ़ोन से कोई भी मित्र बनकर प्राप्त कर सकते हैं|-pdt.kljhashastri@gmail.com-09897701636,09358885616
ReplyDeleteGreat! But when will Full Text Search and "OR" queries be finally available?
ReplyDeleteAs we all know, Google pissed a lot of people off by changing the way GAE bills apps (by instance hours, a la Amazon's EC2, instead of CPU use as was originally the case for App Engine). As a result, many people are paying on the order of 10x what they originally did.
ReplyDeleteI just looked at the free quotas, and they seem pretty generous to me. Who's going over 46 million XMPP calls _per day_? I suppose it's probably the 1GB of daily bandwidth in each direction that people go way over? Or the 100 mails/day? All other quotas seems difficult to surpass.
Admittedly I'd totally bought into the "App Engine sucks" rhetoric, but if you're using that much of Google's resources, shouldn't you be paying them?
That said, I personally know people who have relatively low-traffic GAE apps deployed and who will supposedly be taking them down soon due to cost.
Are they forgetting about the free quota or what? What am I missing???
The go language is not mentioned. Is it still supported?
ReplyDelete@snarfed.org you seem to work for google... no surprise that you are happy with "all the intangibles like the new SLA and infrastructure changes" .. ha ha they are too intangible .. I can bet that SSL support and the old price scheme would be much more appreciated than these intangible things... let's hope google will add some tangible features in the next release !
ReplyDeleteCharging by the instance hours instead of CPU time looks like an evil move. I am seriously looking at migrating my app to EC2 now.
ReplyDelete