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 CCF1518062 for ; Mon, 27 Jul 2015 23:24:46 +0000 (UTC) Received: (qmail 34973 invoked by uid 500); 27 Jul 2015 23:24:34 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 34933 invoked by uid 500); 27 Jul 2015 23:24:34 -0000 Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.incubator.apache.org Delivered-To: mailing list user@ignite.incubator.apache.org Received: (qmail 34923 invoked by uid 99); 27 Jul 2015 23:24:34 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jul 2015 23:24:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B47F71915A7 for ; Mon, 27 Jul 2015 23:24:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 0lyWaLDUplxt for ; Mon, 27 Jul 2015 23:24:23 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 65C8A2156C for ; Mon, 27 Jul 2015 23:24:23 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id EA871120A199 for ; Mon, 27 Jul 2015 16:24:14 -0700 (PDT) Date: Mon, 27 Jul 2015 16:18:49 -0700 (PDT) From: vkulichenko To: user@ignite.incubator.apache.org Message-ID: <1438039129313-723.post@n6.nabble.com> In-Reply-To: References: <1437806503474-716.post@n6.nabble.com> Subject: Re: Question about persistent database MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Louis, You can have one instance of MySQL, load data to Ignite and run SQL queries. Queries will be executed over the data that is already in cache and this data can be partitioned across multiple nodes - this will give you scalability. If you update data in cache, you can write it through to the database via CacheStore implementation. Here are some documentation links that can be useful for you: http://apacheignite.readme.io/docs/cache-queries - Cache Queries API http://apacheignite.readme.io/docs/persistent-store - Persistent Store http://apacheignite.readme.io/docs/data-loading - Data Loading -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-persistent-database-tp715p723.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.