C# Cache / API
I have mvc / c# / razor app that using the following method / class and I found out our developer put this on Views/Shared/Layoutpage.
It looks like it is called this method everytime when the page is refreshed. As a result, it is super easy to max out the API usage.
My question is: What is the best practice to use cache in c# to reduce this usage? In general, the layoutpage will be loaded as usual.
Please show me how it works in codes/c#. Thanks
public static string GetLatitiudeByIP(string ip)
{
string returnValue = "34.028623";
XmlDocument foo = new XmlDocument();
foo.Load(String.Format("http://api.ipstack.com/" + ip + "?access_key=7efaasdfasdfa
XmlNode latitudeNode = foo.SelectSingleNode("/res
if(latitudeNode != null)
{
returnValue = latitudeNode.InnerText;
}
return returnValue;
}
It looks like it is called this method everytime when the page is refreshed. As a result, it is super easy to max out the API usage.
My question is: What is the best practice to use cache in c# to reduce this usage? In general, the layoutpage will be loaded as usual.
Please show me how it works in codes/c#. Thanks
public static string GetLatitiudeByIP(string ip)
{
string returnValue = "34.028623";
XmlDocument foo = new XmlDocument();
foo.Load(String.Format("http://api.ipstack.com/" + ip + "?access_key=7efaasdfasdfa
XmlNode latitudeNode = foo.SelectSingleNode("/res
if(latitudeNode != null)
{
returnValue = latitudeNode.InnerText;
}
return returnValue;
}
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
IMO, why is this even in the view? I would move this logic to a service layer where you can share the code between disparate projects.
Next, what exactly do you want to cache? You'll need to figure out how long you want whatever that is cached (i.e. figure out a cache invalidation process). Keep in mind that the more you cache, the more memory you consume on your server.
Next, what exactly do you want to cache? You'll need to figure out how long you want whatever that is cached (i.e. figure out a cache invalidation process). Keep in mind that the more you cache, the more memory you consume on your server.
Extending the previous comment, caching is great so long as cache data avoids becoming stale...
In other words, your cached value becomes old + the actual data has changed.
For caching, you just have to ensure you expire your cache at a rate faster than actual API data changes, so you make API calls when required, to actually pull truly new data.
For GEO coordinates, likely this data will change very infrequently, so caching this data to reduce API calls will likely be good + have few problems with data differences between your cache + API you're calling.
In other words, your cached value becomes old + the actual data has changed.
For caching, you just have to ensure you expire your cache at a rate faster than actual API data changes, so you make API calls when required, to actually pull truly new data.
For GEO coordinates, likely this data will change very infrequently, so caching this data to reduce API calls will likely be good + have few problems with data differences between your cache + API you're calling.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial