You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by chevy <ch...@target.com> on 2016/11/08 09:09:29 UTC
Query on using Ignite as persistence data and processing layer
Hi,
I am looking at a feasibility of using Ignite as a persistence layer
instead of a mySql/Postgres db where we do lot of processing before sending
data to our rest-api.
1. Is it good to use ignite as a storage?
2. Is it efficient to do so much processing of data in ignite?
3. What is the availability quotient of ignite/ probability of node going
down causing data loss?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-on-using-Ignite-as-persistence-data-and-processing-layer-tp8775.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Query on using Ignite as persistence data and
processing layer
Posted by vkulichenko <va...@gmail.com>.
No, this is not available yet. Here is the corresponding ticket:
https://issues.apache.org/jira/browse/IGNITE-961
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-on-using-Ignite-as-persistence-data-and-processing-layer-tp8775p8858.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Query on using Ignite as persistence data and
processing layer
Posted by chevy <ch...@target.com>.
One more query Val, Is Node.js support for Ignite (client and server) available?
--
Regards,
Chetan.
From: "vkulichenko [via Apache Ignite Users]" <ml...@n6.nabble.com>
Date: Wednesday, November 9, 2016 at 3:31 AM
To: "Chetan.V.Yadav" <Ch...@target.com>
Subject: [EXTERNAL] Re: Query on using Ignite as persistence data and processing layer
Hi,
It's fine to use Ignite as the main and only data storage for your application, but Ignite is not a persistence storage. Data is in memory, so there is always a chance for data loss. If this is something that you can't live with, then do not rip and replace, but use Ignite with a persistence store underneath.
-Val
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Query-on-using-Ignite-as-persistence-data-and-processing-layer-tp8775p8795.html
To unsubscribe from Query on using Ignite as persistence data and processing layer, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8775&code=Y2hldGFuLnYueWFkYXZAdGFyZ2V0LmNvbXw4Nzc1fC02OTIwMTYzODA=>.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-on-using-Ignite-as-persistence-data-and-processing-layer-tp8775p8812.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Query on using Ignite as persistence data and processing layer
Posted by vkulichenko <va...@gmail.com>.
Hi,
It's fine to use Ignite as the main and only data storage for your
application, but Ignite is not a persistence storage. Data is in memory, so
there is always a chance for data loss. If this is something that you can't
live with, then do not rip and replace, but use Ignite with a persistence
store underneath.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-on-using-Ignite-as-persistence-data-and-processing-layer-tp8775p8795.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.