Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Goodbye, Google App Engine

carlosble.com

Post reply on HN
Print view View original

91–100 of 102 posts

Re: Goodbye, Google App Engine

#91

Post by wallflower »

ivanzhao wrote: post #12

I just launched my app 4 days ago (threewiki.com) and its backend is using GAE (Python + Tornado). On the second day, it was featured on TheNextWeb front page and the server got TONS of traffic. It scared me a bit, and I quickly change the daily max quota to $10. Anyways, GAE handles everything very gracefully. Over 70% of our users use either Facebook or Twitter to login and it hasn't been a problem at all. I always…

Congrats on the highlight by CreativeApps!

http://www.creativeapplications.net/games/3-degrees-of-wikip...

Re: Goodbye, Google App Engine

#92

Post by gcv »

jimrandomh wrote: post #64

There are a lot of apologists here, and they're all missing the point. Google App Engine has a large number of random issues and limitations which, while they each individually seem like they ought not to matter, add up to a substantial risk for a project running on it. I'm currently working on a project with a web component, and considered GAE. I chose not to use it, because some of the stuff I encountered in the do…

I'm not an App Engine apologist, although I'm seriously evaluating it for my current project. That said, could you please clarify the following points:

1. "You're supposed to handle exceptions from the datastore? Really?" — Are you saying you don't handle exceptions when your regular relational database throws them? I've seen Sybase and MySQL blow up with depressing regularity, and have had to write exception-recovery code for them.

2. "No https with a domain?" — What stops you from making .appspot.com" rel="nofollow">https://.appspot.com the handler for forms which read sensitive information? You can submit the form with XHR, have the server send back a structured response (perhaps as JSON), and deal with it with JavaScript on the client. I admit that it's annoying (you need different form submit targets in development and production), but it shouldn't be a deal-breaker unless you need your entire site to use SSL.

(If you do need your entire site to use SSL, then the appspot domain limitation obviously sucks. If that's the case though, then you're probably doing something with finance, and the datastore's transaction semantics probably cannot work for you at all.)

Re: Goodbye, Google App Engine

#93

Post by mbrenig »

bemmu wrote: post #81
mbrenig wrote: post #72

Earlier quoted context omitted.

Can you share general numbers on this? I'm interested in which quotas you're spending money on the most.

This is for yesterday. Resource Used Free Billable Charge CPU Time: $0.10/CPU hour 46.03 6.50 39.53 $3.96 Bandwidth Out: $0.12/GByte 2.54 1.00 1.54 $0.19 Bandwidth In: $0.10/GByte 0.76 1.00 0.00 $0.00 Stored Data: $0.005/GByte-day 750.78 1.00 749.78 $3.75 Recipients Emailed: $0.0001/Email 0.00 2,000.00 0.00 $0.00 Total: $7.90

Thank you.

Re: Goodbye, Google App Engine

#94

Post by ivanzhao »

foljs wrote: post #84
ivanzhao wrote: post #12

I just launched my app 4 days ago (threewiki.com) and its backend is using GAE (Python + Tornado). On the second day, it was featured on TheNextWeb front page and the server got TONS of traffic. It scared me a bit, and I quickly change the daily max quota to $10. Anyways, GAE handles everything very gracefully. Over 70% of our users use either Facebook or Twitter to login and it hasn't been a problem at all. I always…

"""I always think if your site can't be host by GAE, then it's probably not very scalable at the first place. I""" Well, your site is basically one static page. Do you really feel qualified discussing GAE?

Of course I do. The ENTIRE game logistics runs on GAE, the iPhone stores zero data except a user key.

Re: Goodbye, Google App Engine

#95

Post by cmelbye »

foljs wrote: post #84
ivanzhao wrote: post #12

I just launched my app 4 days ago (threewiki.com) and its backend is using GAE (Python + Tornado). On the second day, it was featured on TheNextWeb front page and the server got TONS of traffic. It scared me a bit, and I quickly change the daily max quota to $10. Anyways, GAE handles everything very gracefully. Over 70% of our users use either Facebook or Twitter to login and it hasn't been a problem at all. I always…

"""I always think if your site can't be host by GAE, then it's probably not very scalable at the first place. I""" Well, your site is basically one static page. Do you really feel qualified discussing GAE?

its backend is hosted by GAE

So, all of the dynamic backend code powering the app is running on Google App Engine.

Re: Goodbye, Google App Engine

#97

Post by ivanzhao »

wallflower wrote: post #91
ivanzhao wrote: post #12

I just launched my app 4 days ago (threewiki.com) and its backend is using GAE (Python + Tornado). On the second day, it was featured on TheNextWeb front page and the server got TONS of traffic. It scared me a bit, and I quickly change the daily max quota to $10. Anyways, GAE handles everything very gracefully. Over 70% of our users use either Facebook or Twitter to login and it hasn't been a problem at all. I always…

Congrats on the highlight by CreativeApps! http://www.creativeapplications.net/games/3-degrees-of-wikip...

Thanks. Did you also posted on Reddit? Your name is so familiar.

Re: Goodbye, Google App Engine

#98

Post by foobarbazoo »

krosaen wrote: post #39
powera wrote: post #35

A few of these points are just ridiculous: 1) If you want "SQL and Joins", use SQL. This is like complaining that you can't play Halo on Linux. 1A) There isn't full text search. If you need full text search, use a system with full text search as a feature. 2) Some of the points are out of date (or will be out of date soon). The 30 second limit for cron jobs will be 10 minutes after the next release. As noted, the 100…

I've gotten full text search working using techniques similar to those described here: http://www.billkatz.com/2009/6/Simple-Full-Text-Search-for-A...

I find it amusing that Google doesn't have a full-text search engine. I seem to remember them having code to do that...somewhere. Hmm.

Re: Goodbye, Google App Engine

#99

Post by zmmmmm »

grandalf wrote: post #71
zmmmmm wrote: post #55

Earlier quoted context omitted.

This is what I've never understood about GAE. If you're small, GAE is free, but then, you could host anywhere for peanuts - just buy a linode or a small EC2 instance, it doesn't really matter. Once your site becomes big, cost is going to matter and GAE is as expensive as anyone else, last time I looked, quite a bit more expensive. So there is really not much advantage, it is only free when it doesn't matter, and when…

I'm curious how the billing breaks down for your app. Is it mostly CPU quota? Or bandwidth? etc.

For me it's CPU and bandwidth (it's lots of real-time image transformations). So if you look at GAE it's just about the same as EC2 (0.10 / hr for CPU, 0.10/0.12 GB for data, 0.15/GB for storage), but there is no "reserved instances" discount which is really significant (unless I'm unaware of it). On balance it's comparable to EC2 but you have way less flexibility.

Re: Goodbye, Google App Engine

#100

Post by alevi »

krosaen wrote: post #34

This hasn't been my experience. Yes, existing techniques for full text search works or things like geolocation queries won't work but there are other[1] techniques[2] that work just as well; it's just not the sql way. Basically, support for multiple set membership queries against a list of tags stored with entities is extremely powerful and if you index properly, you can do a lot of cool things [3]. Plus, you can do…

To your point about incoming mail with attachments > 1mb. The limit is actually 10mb, so you should have no problem mailing photos from smart phones.

http://code.google.com/appengine/docs/python/mail/overview.h... http://code.google.com/appengine/docs/java/mail/overview.htm...

Post reply on HN