Hey guys
I am using autocomplete funcionality with custom list view for adress searches I call our API - where we implemented caching of requests with some expiration, and only when our API doesnt know the answer we ask HERE service. But still as amount of users and overall usage of our apps increase the costs are geting higher and higher.. its already few hundreds of euros monthly..
we are now consuming over 200 000 autosuggest api calls per month...and its growing...
So I am thinking about further optimization.... like don't send each request over 3 letters on _TextChanged event to API and implement some delay like 300ms to slow the flow of api calls and wait until the user really finished writing.. Also I dont want to decrease UI feeling.. so user doesnt think that service is not responding...
Any ideas has somebody try to solve it yet ?
thanks
I am using autocomplete funcionality with custom list view for adress searches I call our API - where we implemented caching of requests with some expiration, and only when our API doesnt know the answer we ask HERE service. But still as amount of users and overall usage of our apps increase the costs are geting higher and higher.. its already few hundreds of euros monthly..
we are now consuming over 200 000 autosuggest api calls per month...and its growing...
So I am thinking about further optimization.... like don't send each request over 3 letters on _TextChanged event to API and implement some delay like 300ms to slow the flow of api calls and wait until the user really finished writing.. Also I dont want to decrease UI feeling.. so user doesnt think that service is not responding...
Any ideas has somebody try to solve it yet ?
thanks