Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76E43D3FD for ; Tue, 27 Nov 2012 23:18:04 +0000 (UTC) Received: (qmail 67492 invoked by uid 500); 27 Nov 2012 23:18:02 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 67414 invoked by uid 500); 27 Nov 2012 23:18:02 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 67406 invoked by uid 99); 27 Nov 2012 23:18:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Nov 2012 23:18:02 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Nov 2012 23:17:55 +0000 Received: by mail-ob0-f176.google.com with SMTP id un3so13298268obb.35 for ; Tue, 27 Nov 2012 15:17:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=j2lVBaFN55KxGc1jOR77WCbcXPEsLR3hjE70yxelQ0Y=; b=UyTDxsJrUzSjlX4ob9qRz1ohKsrYpULVCm2JoFZSHwdFsVuiACSOx6qi+g2NitKj1k Rc0OzmHWAM0soHli5/gIQfYzr1M32Tlgc3qP6IomuDBD502pSsT5yHtdIOD9NeSuWaaq +RceMkupGIMf1N+JGCxFl/Jcz6GZQcVpIovfbqCc06Cfqh784/sd9hrxILLzn8EUVY4m qGd6qsGbU2oKhjyHzd67SVYcCiwYeEnbyV6qOndTo9cR7mRkcNEteTOmhK5F/PDPe/lQ Yunq362gv2baoiELDnJnWcdf5kC2VuiE/LWQFuGIx2CfC09Yk4jHufMcm72ckO9bfADN AOPw== Received: by 10.60.172.13 with SMTP id ay13mr14024488oec.130.1354058254244; Tue, 27 Nov 2012 15:17:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.120.169 with HTTP; Tue, 27 Nov 2012 15:17:14 -0800 (PST) In-Reply-To: <763307E7-E7FA-43CE-AAE1-9C5A65211AED@nimble.be> References: <763307E7-E7FA-43CE-AAE1-9C5A65211AED@nimble.be> From: Ted Dunning Date: Tue, 27 Nov 2012 15:17:14 -0800 Message-ID: Subject: Re: Is Hadoop a good choice for car insurance/telecom provider calculators? To: "general@hadoop.apache.org" Content-Type: multipart/alternative; boundary=bcaec54fb7f63fdba104cf824170 X-Gm-Message-State: ALoCoQnkOumMz1S9TcME5DCoutuRrGe4orXQBpp10GcoIf9sJxbyiNgdoyDH6jQ1tnGTVdMGiqJU X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54fb7f63fdba104cf824170 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable If your computation fits in Excel, then you won't likely see benefits from Hadoop. If your computation becomes thousands to millions of times too large for Excel, then Hadoop might be a great answer. On Tue, Nov 27, 2012 at 12:39 PM, Gabriel Lozano-Moran w= rote: > Hello > > I work for a large consumer organisation and we provide as a service for > our members several calculators where our members can calculate based on > their profile which is the: > > - cheapest energy provider (based on your yearly consumption) > - cheapest car insurance (based on some criteria such as car brand, model= , > age, accident history, =85) > - cheapest telecommunications provider (based on criteria such as the > number of text messages sent per month, =85) > > For each of the calculators we have data for providers. For example we > have from the different telecommunications providers all their subscripti= on > plans that allows us to calculation for you which would be the cheapest > provider. > > We have right now a custom solution build in .NET (C#) that uses Excel an= d > the calculations are performed on several servers. > > We are considering on replacing this solution by a new one and we were > wondering whether switching to Hadoop and Hive ODBC would be a better > choice for these kind of calculations. Or are there better solutions? > > Any help is strongly appreciated. > > With kind regards > > Gabriel Lozano-Moran > > > --bcaec54fb7f63fdba104cf824170--