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

81–90 of 102 posts

Re: Goodbye, Google App Engine

#81

Post by bemmu »

mbrenig wrote: post #72
bemmu wrote: post #62

Earlier quoted context omitted.

I'm paying a similar amount for similar traffic, and I do recall it was a bit cheaper when I had my own server. However I also recall wasting a looot of time configuring and maintaining that server. I'm willing to spend some to save time.

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

Re: Goodbye, Google App Engine

#82

Post by known »

nl wrote: post #31

Does no one read the documentation before deciding to use a platform anymore? App Engine supports Python 2.5. The Python interpreter runs in a secured "sandbox" environment to isolate your application for service and security. The interpreter can run any Python code, including Python modules you include with your application, as well as the Python standard library. The interpreter cannot load Python modules with C co…

I think the author is right. GAE is not suitable for doing serious business.

Re: Goodbye, Google App Engine

#83

Post by slashclee »

Tichy wrote: post #5
arfrank wrote: post #3

#3 isn't true for taskqueue tasks or cron jobs anymore, the deadline is now 10 minutes ( actually will be once 1.4.0 SDK is released in about a week or so ) Also at first glance there is no indication of how the author got to a value of 15k€. My best guess, and a guess at that, is that they put the value of a line of code at 1€ and had to migrate 15k lines, but I hope there is more scientific than than.

He also mentioned that working around GAE set them back 5 months.

This entire article reads like a tutorial about how to make poor decisions.

I mean, if I want to eat a cake, and I know how to make a cake, I'm not going to pull up a recipe for brownies and try to make a cake out of them. This guy made some really bewildering choices; the list of things he clearly wants to do is both silly and frustrating.

"I want to write a site using Django that uses full-text search and multiple-table JOINs so that it takes longer than 30 seconds to load a single page, and Google App Engine won't let me!"

Brilliant.

Re: Goodbye, Google App Engine

#84

Post by foljs »

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?

Re: Goodbye, Google App Engine

#85

Post by foljs »

grandalf wrote: post #70
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…

It's generally not that hard to make it work well... though the datastore issues over the past few months were a real nightmare and could have (and probably did) sink a few businesses. That said, it's a beta product.

"""That said, it's a beta product."""

It always is with Google. When exactly do you expect the "rc"?

Re: Goodbye, Google App Engine

#86

Post by preek »

Incredible how many points this article gathers considering the valid arguments made in the comments[1]. There must be a lot of bad experience (or fear) with this platform.

Personally, I recently had my fair share of problems with the DownloadError, but I knew it would come up (because I read the documentation - and I concur with the limit for scaling reasons). So I built myself a failover decorator relaying the failing requests to a VPS.

Otherwise, I love GAE!

1. For example the top commenter nl with 83 points: http://news.ycombinator.com/item?id=1928148

Re: Goodbye, Google App Engine

#87

Post by foljs »

sahaj wrote: post #78

i'd curious to hear what you switch to and, in about a year, how well it is working out. my buddies and i are working on a time manager for college students and we are having a hard time deciding between RoR and GAE. any insight would be helpful. we are looking for: login manager database capable of up to 50 fields for each user sorting and search capability must cost less than $10/year/user. ps. if you are someone i…

Why is it mostly non-western developers that post those kind of ridiculous "please solve my problem for me" questions?

(btw: non western myself)

Re: Goodbye, Google App Engine

#88

Post by foljs »

lappet wrote: post #28

For all I know, GAE is really easy to develop on. I made this using Django in a couple of hours' time: http://bhoogolvidya.appspot.com/

Yes, I'm sure your one page, one form, application tells a lot of relevant stuff about GAE.

Re: Goodbye, Google App Engine

#89

Post by mike_esspe »

zmmmmm wrote: post #55
mike_esspe wrote: post #52

The biggest problem for me with GAE is cost. Currently I'm paying around $150 per week for around 50k daily active users (~6 million requests per day). I'm almost sure, that i can run the same amount of traffic from $100/month dedicated server.

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…

1) It's hard to move without rewriting the code. 2) It's hard to get a consistent data snapshot without taking your service off for several hours.

Re: Goodbye, Google App Engine

#90

Post by chopsueyar »

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…

Google Checkout Gadget aside, I find it interesting that this is the closest thing Google has to offer for an individual or business to build a hosted online e-commerce presence (https exceptions aside).

Compare that, in terms of functionality and revenue generation, to Yahoo! Store (Viaweb), and it seems like Google really has its priorities with App Engine askew.

Obviously, the scope of Viaweb's functionality is much, much narrower than that of GAE, but what is the purpose of GAE from Google's perspective?

Surely, it is not to create bitchfests for upset developers on tech blogs. It doesn't seem like revenue generation, nor developer satisfaction is a priority, either.

Post reply on HN