Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 25478200B4A for ; Wed, 6 Jul 2016 04:12:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 23E01160A76; Wed, 6 Jul 2016 02:12:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6DE92160A6F for ; Wed, 6 Jul 2016 04:12:02 +0200 (CEST) Received: (qmail 98906 invoked by uid 500); 6 Jul 2016 02:12:01 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 98896 invoked by uid 99); 6 Jul 2016 02:12:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2016 02:12:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3702CC1206 for ; Wed, 6 Jul 2016 02:12:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id jJ1fucW8j2Q1 for ; Wed, 6 Jul 2016 02:11:59 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A5B985F47E for ; Wed, 6 Jul 2016 02:11:58 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 7F8C62BD952A for ; Tue, 5 Jul 2016 18:50:06 -0700 (PDT) Date: Tue, 5 Jul 2016 18:55:18 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1467770118195-6122.post@n6.nabble.com> In-Reply-To: <1467712579496-6097.post@n6.nabble.com> References: <1467712579496-6097.post@n6.nabble.com> Subject: Re: Data Grid versus Compute Grid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 06 Jul 2016 02:12:03 -0000 Hi, Can you please property subscribe to the mailing list so that the community can receive email notifications for your messages? Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 Ramesh wrote > I am unable to understand the motivation for a compute grid. Is it > primarily for providing a clustered computing environment along with > in-memory processing? In other words is there not a lot of overlap between > the two grids? Yes, Compute Grid is for high performant parallel processing and distributed execution. Please refer to the documentation [1] and examples [2] for more details. Note that Compute Grid is highly integrated with Data Grid. For example, you can route closures to the node where particular data is stored, avoiding transferring large data objects across the network [3]. I'm not sure I understand what you mean by "overlap between the two grids". Can you please clarify? [1] https://apacheignite.readme.io/docs/compute-grid [2] https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples/computegrid [3] https://apacheignite.readme.io/docs/collocate-compute-and-data -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-Grid-versus-Compute-Grid-tp6097p6122.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.