The Entry Processor has been introduced in NCache to allow users to execute their code (invocable functions) against a set of cache entries on the server side. NCache fully supports precise execution of Entry Processor regardless of the caching topology being used.
In the usual update scenario, you actually make two network trips to and from the cache. One, to fetch the element to be modified, and the second to save the updated value back into the cache. This is where Entry Processors come in handy: you can modify cache entries on the server side without involving these entries to travel over the network for fetch and update operations. This results in fairly noticeable performance improvement because of the avoidance of network trips and unnecessary consumption of resources.
In case of partitioned topologies, entries are processed on the same node where they reside.
In order to configure Entry Processor follow these steps.
The name of the cache used in this example is demoClusteredCache. Update the cache name according to your own cache.
Make sure Entry Processor has been implemented as described in the Entry Processor section. This assembly will then be deployed using
Install-Module cmdlet enables the user to deploy provider assemblies from the specified assembly path to the deployment folder named 'deploy' in NCache installed directory.
The following example deploys the assembly for a cache named demoCache on server 184.108.40.206 and Port 8251.
Install-Module demoCache -AssemblyPath C:\Provider.dll –Server 220.127.116.11 –Port 8251