Hi Mangesh, If you have the key for your entry then it will be more performant, calling the function, using the API. You achieve this by using the 'withFilter(key)' predicate.
(Java) Clients maintain metadata about where the data is stored for a given key and so they're able to leverage that in this situation. For the REST API, we unfortunately don't have a way to achieve this mapping at the moment, so your REST call will most likely be forwarded to the actual server that holds the data, thus incurring an additional hop penalty. --Jens On Fri, Oct 6, 2017 at 9:17 AM, Mangesh Deshmukh <[email protected]> wrote: > Hi, > > > > If we enable REST APIs, will it be calling a function on partitioned > region on all servers that host this region? Is there a way to optimize > this to go only to the server that hosts the entry? > > > > Would calling the function using REST be less performant than by calling > it using API? > > > > Thanks, > > Mangesh > > > > >
