You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by vkulichenko <va...@gmail.com> on 2015/07/20 21:55:45 UTC
Re: data isolation
Hi,
I think you should create separate caches for different apps. E.g., data for
App1 is stored in app1_cache and data for App2 is stored in app2_cache. If
App1 uses only app1_cache, it will never get access data in app2_cache, and
other way around.
Will this work for you?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/data-isolation-tp670p672.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: data isolation
Posted by vkulichenko <va...@gmail.com>.
Got it.
It looks like each application instance should pick on of the nodes and
always send computation closures to that node. In case this node crashes, it
should switch to another node. I think you can also consider using
replicated cache for this - this way you will have the whole data set on all
nodes.
Is this what you're looking for?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/data-isolation-tp670p698.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: data isolation
Posted by vkulichenko <va...@gmail.com>.
I'm not sure I correctly understand what you're trying to achieve. Can you
please describe your use case in more detail?
Do you have data that needs to be isolated for a particular app and another
set of data that can be shared between apps? If so, you can still have
separate caches for per-cache data and for shared data. Is this the case?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/data-isolation-tp670p685.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.