Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 32884 invoked from network); 24 Feb 2011 09:33:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2011 09:33:02 -0000 Received: (qmail 23444 invoked by uid 500); 24 Feb 2011 09:33:01 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 22035 invoked by uid 500); 24 Feb 2011 09:32:59 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 21957 invoked by uid 99); 24 Feb 2011 09:32:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 09:32:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cbsmith@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 09:32:50 +0000 Received: by wwi14 with SMTP id 14so16797wwi.29 for ; Thu, 24 Feb 2011 01:32:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=S+9gJ7o1/in26A9e31l4fa9t9K69aNwAIT6ZDBYY+fA=; b=BvgJ9eIDBq6t3iIJM8YB6M8j54tbjc2U8Wle9TbWsWEZfNgT15ubaWU4GfwN2sNAUU 1l2996U1OEUEi0UUq3chmWVNxPxPDFm9McysGuvUYHuosobU3HLGPrDmP8v+uW1IHZA4 hnAQnf2v4AZOuR5jsM4f+z3zGUfybiwTSLEns= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=CIY5iElkCZWo3uYIwJo1jI617tJLjSe6pfFvnrS7ntlzWFmZpvOpL6PnMBFYzrcupz Y3S3N1ZUCJ5/plDdcM8vWrt/OmdDrg49u7COoU8JMmG0nyGG8qwjwuIgd9SiKr6sRFqy 8IKukAdVSNkBKnpsgdDUGAy/W73eLbQCClMrY= Received: by 10.216.55.145 with SMTP id k17mr5788317wec.48.1298539948150; Thu, 24 Feb 2011 01:32:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.49.1 with HTTP; Thu, 24 Feb 2011 01:32:08 -0800 (PST) In-Reply-To: <31001290.post@talk.nabble.com> References: <31001290.post@talk.nabble.com> From: Christopher Smith Date: Thu, 24 Feb 2011 01:32:08 -0800 Message-ID: Subject: Re: using Hadoop as an integration platform To: common-dev@hadoop.apache.org Cc: smjain , core-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hadoop provides standardized interfaces/formats/execution models/etc., so it can be used for integration (and indeed, I've done that). However, it differs from most ESB's in that it is very batch oriented, rather than real-time/streaming/queuing oriented. Consider whether your integration needs fit in to a batch model. On Wed, Feb 23, 2011 at 11:43 PM, smjain wrote: > > Hi, > > I have been suggested that we can use Hadoop as an integration bus similar > to an ESB. > > My notion of Hadoop is that it is useful for crunching huge data and mainly > data mining. > > I think integration different Apps is a domain of ESB and not Hadoop.. > > Anyone has suggestions/thoughts. -- Chris