Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A1B518288 for ; Tue, 16 Feb 2016 21:19:39 +0000 (UTC) Received: (qmail 53390 invoked by uid 500); 16 Feb 2016 21:19:39 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 53344 invoked by uid 500); 16 Feb 2016 21:19:39 -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 53334 invoked by uid 99); 16 Feb 2016 21:19:39 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Feb 2016 21:19:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CB38EC0599 for ; Tue, 16 Feb 2016 21:19:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Lrz0PDVMN1mx for ; Tue, 16 Feb 2016 21:19:36 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 454A85FB66 for ; Tue, 16 Feb 2016 21:19:36 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 04A5320E0FC9 for ; Tue, 16 Feb 2016 13:13:01 -0800 (PST) Date: Tue, 16 Feb 2016 13:07:41 -0800 (PST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1455656861884-3045.post@n6.nabble.com> In-Reply-To: References: <1455242645612-2970.post@n6.nabble.com> <1455254196345-2971.post@n6.nabble.com> <1455289295611-2984.post@n6.nabble.com> <1455314049688-2992.post@n6.nabble.com> Subject: Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Gareth, gcollins wrote > I guess the SpiQuery can help me part of the way potentially, but it > doesn't give me the control to manage internal memory structure, > replication, custom persistence etc. What kind of control do you expect? Can you give an example? In general, almost everything in Ignite is customizable and pluggable. E.g., to customize backup node assignments you can implement your own AffinityFunction, for custom persistence implement CacheStore interface. Can you clarify what you mean by "internal memory structure"? Can you create an Ignite cache (or caches) under the hood and provide your own APIs and/or services around it? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Migrating-From-Hazelcast-Service-Interface-To-Apache-Ignite-Service-Interface-tp2970p3045.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.