[
https://issues.apache.org/jira/browse/IGNITE-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205838#comment-17205838
]
Marty Jones edited comment on IGNITE-13037 at 10/1/20, 9:51 PM:
----------------------------------------------------------------
I currently use NCache for our caching provider. They support near caches so I
was hoping to transition to Apache Ignite and not lose any current
functionality.
We gain a huge performance benefit of using a near cache since we only have to
take the performance hit of pulling down the cache item from the remote cache
one time for most of our objects versus having to pull the remote object down
every time we need access to the object.
was (Author: marty.jo...@newportgroup.com):
I currently use NCache for our caching provider. They support near caches so I
was hoping to transition to Apache Ignite and not lose any current
functionality.
We gain a huge performance benefit of using a near cache since we only have to
take the performance hit of pulling down the cache item from the remote cache
one time for most of our objects.
> .NET: Thin Client Near Cache
> ----------------------------
>
> Key: IGNITE-13037
> URL: https://issues.apache.org/jira/browse/IGNITE-13037
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET
>
> Add near caching for thin clients:
> * Clients can subscribe to change notifications for specific keys
> * Clients use partition awareness to route subscriptions to primary nodes
> * Use existing Thick .NET Client near caching mechanism to handle updates on
> the server side
> * Eviction policy is to be handled by the client code (because multiple
> servers are involved)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
