Besides, what is the difference in functionality between storage disabled cluster members and Extend client processes(non-clustered)? I can invoke Entry Processor and Invocable from either of them, right?EntryProcessor - yes
For Invocable, in case of Extend client, if one cannot choose a member and it will always invoked on the proxy, then Invocable cannot be used if we want it to run on the node that processing data resides on, isn't it? Thanks.That is correct, but you can work this around but having InvocableTask from Extend client to use invocation API and send another task/tasks. Proxy is a member of cluster so your first task will have full access to cluster invocation API.
alexey.ragozin wrote:That's a strange question. I would have said that having data affinity makes it even more likely that you will use invocables. You can efficiently target an invocable to a specific cluster member and be sure that all the data that the invocable needs is on that member. Even from an extend client it is easy to do a two stage invocable that can target specific members. Our project relies heavily on data affinity and our entire client API uses invocables, aggregators and occasionaly entry processors. The invocables allow the client side to be a very thin layer with minimal direct cache interaction - most of the work is done on extend proxies.
BTW are you sure you really need invocation with data affinity?