Dang, I was four hours late to the party. I wanted to mention that we'd already beat that horse.
On Thu, Jun 9, 2011 at 20:06, Ikai Lan (Google) <[email protected]> wrote: > You're about two days late to the party. Read the earlier comments in this > thread ... > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog: http://googleappengine.blogspot.com > Twitter: http://twitter.com/app_engine > Reddit: http://www.reddit.com/r/appengine > > > On Fri, Jun 10, 2011 at 7:23 AM, Andrei <[email protected]> wrote: >> >> Here is another piece of info from guy who worked 10 years for Google >> http://rethrick.com/#waving-goodbye >> >> And this relates to GAE >> >> Speed >> >> Here is something you've may have heard but never quite believed >> before: Google's vaunted scalable software infrastructure is obsolete. >> Don't get me wrong, their hardware and datacenters are the best in the >> world, and as far as I know, nobody is close to matching it. But the >> software stack on top of it is 10 years old, aging and designed for >> building search engines and crawlers. And it is well and truly >> obsolete. >> >> Protocol Buffers, BigTable and MapReduce are ancient, creaking >> dinosaurs compared to MessagePack, JSON, and Hadoop. And new projects >> like GWT, Closure and MegaStore are sluggish, overengineered >> Leviathans compared to fast, elegant tools like jQuery and mongoDB. >> Designed by engineers in a vacuum, rather than by developers who have >> need of tools. >> >> In the short time I've been outside Google I've created entire apps in >> Java in the space of a single workday. (Yes, you can program as >> quickly in Java as in Ruby or Python, if you understand your tools >> well.) I've gotten prototypes off the ground, shown it to people, or >> deployed them with hardly any barriers. >> >> On Jun 7, 9:59 am, Joshua Smith <[email protected]> wrote: >> > http://www.theregister.co.uk/2011/06/07/inside_google_app_engine/ >> > >> > Nice overview, and I didn't see any glaring errors. I'll be keeping a >> > link to this to pass along whenever anyone asks me what GAE is (and isn't). >> > An interesting observation was that many apps spill into non-GAE >> > infrastructure when they need some functionality that GAE doesn't offer. >> > That's true of several of our apps: one of my apps interfaces with S3 >> > heavily because I wrote it before BlobStore existed; another uses GAE only >> > as a massively scalable front-end "lobby" and scheduler, for access to >> > non-GAE servers (in a private data center, and in EC2 when the private data >> > center fills up). >> > >> > Also, it was interesting to see the coverage of App Scale. I was >> > familiar with AETyphoon, but not App Scale. Nice to know there are options >> > if google makes some really bad decisions about their pricing model in the >> > coming months. >> > >> > -Joshua >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
