Best Practice: Hadoop vs Google App Engine

[Alex McLintock <al...@gmail.com>]

Hi Folks,

I'm considering the pros and cons of Google App Engine compared to
Hadoop/Hbase/Hive/Cascading/Amazon EC2 .

Has anyone looked into this question and tried to come up with
reasoned argument why Hadoop is better? If not, would this mailing
list be a good place to start discussing it?

Basically the main advantage of using GAE is that you don't have to
worry about setting up a cluster, or distributed database, or anything
like that - it is done for you. But you are sort of tied in to
google's way of doing things.

Of course hadoop doesn't help at all with actual web serving. It's
latency is too high.

Alex

Re: Best Practice: Hadoop vs Google App Engine

[Jeff Zhang <zj...@gmail.com>]

You can have more control on hadoop, you can create your own cluster with
hadoop.
Although hdfs's latency is high, HBase is a good choice for real time
application.


Jeff Zhang


On Wed, Nov 4, 2009 at 4:17 AM, Alex McLintock <al...@gmail.com>wrote:

> Hi Folks,
>
> I'm considering the pros and cons of Google App Engine compared to
> Hadoop/Hbase/Hive/Cascading/Amazon EC2 .
>
> Has anyone looked into this question and tried to come up with
> reasoned argument why Hadoop is better? If not, would this mailing
> list be a good place to start discussing it?
>
> Basically the main advantage of using GAE is that you don't have to
> worry about setting up a cluster, or distributed database, or anything
> like that - it is done for you. But you are sort of tied in to
> google's way of doing things.
>
> Of course hadoop doesn't help at all with actual web serving. It's
> latency is too high.
>
> Alex
>