[
https://issues.apache.org/jira/browse/IGNITE-14976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368072#comment-17368072
]
Ivan Fedorenkov commented on IGNITE-14976:
------------------------------------------
The implementation that could be considered as a starting point:
https://github.com/killergti/ignite-pet-project/tree/cache-keys-distribution-tracker
> Ignite cache keys distribution tracker
> --------------------------------------
>
> Key: IGNITE-14976
> URL: https://issues.apache.org/jira/browse/IGNITE-14976
> Project: Ignite
> Issue Type: New Feature
> Components: cache
> Affects Versions: 2.10
> Reporter: Ivan Fedorenkov
> Priority: Major
>
> Based on the Apache Ignite Summit presentation.
> There is a use-case when a user may want to keep track of the up-to-date
> subset of cache keys that a node is responsible for. For example, if each
> node must subscribe in external system on updates, but only for those cache
> keys that the node is responsible for (primary or backup).
> Why can't an external system use Ignite Data Streamer or Cache puts? Because
> this is impossible for many legacy systems or systems where user can't
> control the source of events (e.g. some web service).
> Why is this useful? Data locality principle for subscriptions. Reduces the
> amount of network traffic.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
