Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 20675 invoked from network); 4 Nov 2009 12:40:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Nov 2009 12:40:25 -0000 Received: (qmail 29943 invoked by uid 500); 4 Nov 2009 12:40:23 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 29847 invoked by uid 500); 4 Nov 2009 12:40:22 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 29837 invoked by uid 99); 4 Nov 2009 12:40:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2009 12:40:22 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zjffdu@gmail.com designates 209.85.160.50 as permitted sender) Received: from [209.85.160.50] (HELO mail-pw0-f50.google.com) (209.85.160.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2009 12:40:13 +0000 Received: by pwi4 with SMTP id 4so3349363pwi.29 for ; Wed, 04 Nov 2009 04:39:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2Kkdp4ApQZag0zAqvfnD6TcDfg/TcVomalTcKLdiSwM=; b=WBxU2MVcSswuvYlSt4IX1lU00zgKKinjjtUH5eyCX63DnSwH6fJK60cUjpr2RUDonE AOFB8Wlj84LW67v0RozwPXRox4n0k7W6RyS+LDQV4Yg9agUehmpzOOJP5Bz5DHJsq/h1 BN8iY9vTwJ7NKDz6dowukAKvdDM4hNqJqqynQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=B3bp7VDeoHTdzY2Suna82nqJyLM39t4M+dX8pWxWItJcDXTmk5dswqr0y08gaSzsSd gM7hoMgAvG8J28xS+W5NyTloFPYcjlXU6CtC3jdf1n9zZyEQ6l71AzDhkA22ynP2i1L+ 5Ybj3iNkswjQhLdsX6dBgkbW4vSSbHI92bKsI= MIME-Version: 1.0 Received: by 10.142.55.10 with SMTP id d10mr143324wfa.250.1257338392542; Wed, 04 Nov 2009 04:39:52 -0800 (PST) In-Reply-To: References: Date: Wed, 4 Nov 2009 04:39:52 -0800 Message-ID: <8211a1320911040439l160b10few932bc10ea35b7155@mail.gmail.com> Subject: Re: Best Practice: Hadoop vs Google App Engine From: Jeff Zhang To: common-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636b2bb003ffdac04778ae866 X-Virus-Checked: Checked by ClamAV on apache.org --001636b2bb003ffdac04778ae866 Content-Type: text/plain; charset=UTF-8 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 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 > --001636b2bb003ffdac04778ae866--