I am implementing a high-traffic web application that uses a lot of REST APIs for its level of access to data from a cloud database. I told the client because it implements REST and does not provide it.
REST APIs are implemented both on the server side and on the client side, and I need to find a good caching solution. The application runs on a web farm, so I tend to use distributed caching like memcached. This caching solution should look like a proxy between my application and the REST APIs and support both the client and server side.
For example, if I make a call to update a record that I would update using REST, and I would like to keep the updated record in cache, so the next calls to this record will not require an additional call to external REST services.
I want to minimize REST calls as much as possible, and I will need to store the data exactly as I can, but it should not be 100% accurate.
What is the best solution for this caching proxy? Is this a standalone application that runs on one of the servers with a local cache or is embedded in the current solution using distributed caching? what ideas, suggestions or problems do you have.
Thanks,
source
share