TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why Google App Engine Rocks: A Google Engineer’s Take

50 点作者 cjdrake大约 9 年前

12 条评论

johansch大约 9 年前
App Engine is brilliant and strangely under-appreciated at HN, I think. (A cynical person might thank that it&#x27;s AWS &quot;devops&quot; people protecting their jobs, but I guess it&#x27;s more likely that the cause is groupthink.)<p>Last summer I switched jobs from a company where we developed loads of cloud thingies ourselves, because there really weren&#x27;t any good options around ten years ago when we started a product line that needed a high quality global service (involving processing, networking and storage). We had a lot of fun basically building our own little (if 5000+ machines qualifies as little) AWS&#x2F;Google-style Cloud. I heard about Amazon Dynamo in 2007 and then we basically re-implemented it ourselves. We added lots of neat features like datacenter-aware global replication, etc.<p>When I joined the new company last June, it was basically just me. A few months later we hired a great python dev. I&#x27;m so happy to find that the level of the openly available products&#x2F;services had caught up <i>quite</i> a bit by then, enabling us not to spend so much time on just making sure things were available all of the time, and ~infinitely scalable.<p>I spent <i>a lot</i> of time evaluating AWS vs GC, but my inevitable conclusion was that.. in a small company where you don&#x27;t want to invest in a 24&#x2F;7&#x2F;365 devops team you should go for the Google App Engine.<p>I would really like it if Google found some pragmatic way to make App Engine work inside China though, at least for companies that have chinese ICP permits.<p>(Why hasn&#x27;t AWS launched a PaaS? Lambda is so neutered that it doesn&#x27;t really count.)
评论 #11646937 未加载
评论 #11646787 未加载
评论 #11647286 未加载
neals大约 9 年前
Is Google App Engine under performing? I wonder why do they would need a fluff marketing piece like this.<p>I hope they&#x27;re not in trouble or anything, I have been moving my project from VPS over to GCM for the past year now. I love it.
评论 #11646853 未加载
评论 #11647247 未加载
评论 #11647031 未加载
NearAP大约 9 年前
I believe I&#x27;ve made this comment before - Google App Engine is good and quickly allows you to get a proof of concept off the ground. But the documentation SUCKs big time - the language is obtuse, the documentation is repeated in multiple places (meaning different paths to documentation explaining the same thing in different ways), and it is not uncommon to find that the documentation is not current.
评论 #11646833 未加载
oxplot大约 9 年前
A trend of comments I see whenever App Engine is mentioned is how limiting App Engine platform is and how it doesn&#x27;t have MySQL, etc. No one seem to ever mention scalability? App Engine is built for just that! Datastore is infinitely salable so is the application and every other API on GAE. I can spend an hour writing an app from scratch that scales infinitely on GAE without a thought. I personally do not know of <i>any</i> other PaaS (e.g. Openshift, Heroku) that&#x27;s capable of doing that unless you spend a month learning ins and outs of devops for that particular platform.<p>EDIT: Also the Datastore is replicated in multi data centers and again, you don&#x27;t have to think about backups either.
评论 #11648640 未加载
democracy大约 9 年前
I believe many see AWS offer as &quot;we have the same *nix boxes you already have but cheaper&#x2F;on-demand&#x2F;easily scalable&quot;. Plus nice feature as local storage of your data (can be a legal requirement for some industries). Create an account and start deploying now with the smallest investment and commitment.<p>GAE on the other hand is &quot;we can solve your scalability problems&quot; that many simply don&#x27;t have and &quot;you should write&#x2F;re-write your apps to use our framework&quot; which is a red flag to many as well.
评论 #11647157 未加载
评论 #11648646 未加载
ocdtrekkie大约 9 年前
A Google engineer&#x27;s take on a Google product? I don&#x27;t feel like this testimonial holds a lot of real value. Why not have someone who isn&#x27;t being paid by Google tell you that Google products are cool?
评论 #11646928 未加载
评论 #11647097 未加载
NearAP大约 9 年前
One other &#x27;thing&#x27; - there are some services that you have to enable billing before they are available on app engine. Google also typically gives you a 30 day&#x2F;$XXX credit for it. That is a nice feature. The &#x27;challenge&#x27; for me is that typically, at this point I&#x27;m still trying to test out my code and basically have no traffic so the $200 credit basically becomes a waste. It would be nice if one could be allowed to &#x27;decide&#x27; when to use this credit. At my testing&#x2F;experimenting&#x2F;design phase, the free quota would be enough for me or I would be willing to pay out of pocket (since I&#x27;m still testing I would keep the amount to the barest minimum).
kevando大约 9 年前
According to my depreciated appengine console, I would not say that Google thinks &quot;App Engine Rocks.&quot;
评论 #11646730 未加载
评论 #11646732 未加载
balls187大约 9 年前
Just logged into my GAE Console to see how my old apps were doing, and was treated to this:<p><a href="https:&#x2F;&#x2F;annotate.driftt.com&#x2F;view?i=7zvk40ibtjaaxhs%2F2016-05-06_at_1.57_PM.png%2F" rel="nofollow">https:&#x2F;&#x2F;annotate.driftt.com&#x2F;view?i=7zvk40ibtjaaxhs%2F2016-05...</a><p>-----<p>If you get that error, somewhere you need to agree to new T&#x27;s and C&#x27;s. The site doesn&#x27;t redirect your properly, so you need to click around until you are prompted to agree.<p>Pretty cool to see my simple little GAE Emailing app I wrote for my startup back in 2012 was cranking away 3 years later.
评论 #11646698 未加载
评论 #11646944 未加载
filleokus大约 9 年前
Hehe, we&#x27;re running GAE at work and I&#x27;m constantly looking for other options &#x2F; trying to persuade management to spend the time on migration. I spend 8-12 hours a day fighting with GAE in one way or another, even though I very well might experience the &quot;green is grasser&quot; symptom.<p>Many things are nice with App Engine, outlined in the post. But so many things are not nice:<p>- For us the performance characteristics for some queries in the NDB (NoSQL datastore) have really left much to be wanted.<p>- The inability of calling C-libraries from Python code (except those provided by Google, they provide standard stuff like cPickle etc)<p>- The UI for logs &#x2F; querying the database &#x2F; admin is quite bad and buggy. Can&#x27;t really use it in Safari at all (might very well be the wrong doing of Safari, but still)<p>- Limitations in how long functions &#x2F; tasks can run. I&#x27;ve spent all of my Friday night tonight (I&#x27;m in CET) re-writing code for a batch-processing task that took just above the hard imposed limit of 10 minutes to run. According to the docs an exception is to be thrown when the task is nearing its limit but most of the time (intermittently…) the exception is not thrown and just kills the process…<p>- Limited community &#x2F; toolset. Using GAE feels somewhat like using something really old or obscure, quite few SO questions&#x2F;answers (the upside is that many of them are written by Gudio, which lead the NDB project before quitting from Google), and extremely limited third party tools &#x2F; plugins for enhancing the developer experience. For example I haven&#x27;t found any good way, except the GAE provided one, to do performance profiling.<p>- GAE has somewhat of a bad rep in some parts of the Python community I&#x27;ve found. A couple of Python libraries I&#x27;ve tried to use have not worked and then I&#x27;ve found bug reports where the maintainers have explicitly stated that GAE is not supported because of some limitation they have imposed. The biggest example I can come up with right now is probably Requests<p>With that said however, I feel like Google has started giving GAE more love recently. The documentation seems to improve, the dashboards&#x2F;web UI:s have undergone major rework (not all of them improvements per se but still!). I actually said to my management a while ago that we need to move away from GAE in the medium term (1-2 years) because I feared that Google would start to &quot;sunset&quot; GAE. I wouldn&#x27;t say that is the case today, but I could not go so far as to say that I would recommend GAE.<p>GAE is a very nice platform in many ways, but very limited. The tradeoffs for all the ease is quite high and should probably be considered very carefully before picked.
评论 #11648698 未加载
评论 #11647630 未加载
dominotw大约 9 年前
&gt;Some were a LAMP stack on a managed hosting service. Some were running as a cron job on someone’s workstation.<p>All that whiteboard interview pedantry doesn&#x27;t seem to shield them devs who don&#x27;t know how to deploy a basic production grade app. But hey they were able to memorize tree inversions before interviews so thats good.
diyseguy大约 9 年前
They&#x27;re probably going to end of life it like everything else they get bored with. I can&#x27;t imagine any sane business would risk putting any amount of development time investment into their stuff.
评论 #11646967 未加载
评论 #11646995 未加载
评论 #11647008 未加载