Systems and methods for caching of managed content in a distributed environment using a multi-tiered architecture
Embodiments as disclosed provide a distributed caching solution that improve the performance and functionality of a content management platform for sites that are physically or logically remote from the primary site of the content management platform. In particular, according to embodiments, a remote cache server may be associated with a remote site to store local copies of documents that are managed by the primary content management platform. Periodically, a portion of the remote site's cache may be synchronized with the content management platform's primary site using an extensible architecture to ensure that content at the remote cache server is current.
1. A system for remote caching, comprising:
a remote cache system for use with a primary content management system for managing content, including:
a cache;
a processor;
a data store for storing metadata corresponding to content stored in the cache, wherein the content in cache comprises content managed by the primary content management system; and
a non-transitory computer readable medium, comprising instruction for: a remote client transfer module for:
receiving a first request to access content, wherein the first request is associated with a user;
accessing the data store to determine if first metadata associated with the requested content is stored in the data store;
sending a first request to a primary content transfer module associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store;
receiving a first response from the primary content transfer module including second metadata;
comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;
if the version of the content stored in the cache is the current version, providing the content in the cache in response to the first request;
if the version of the content stored in the cache is not the current version sending a second request for the current version of the content to the primary content transfer module;
receiving the current version of the content;
storing the current version of the content in the cache; and
providing the current version of the content in response to the first request; and the primary content transfer module for:
receiving the first request associated with the content from the remote client transfer module;
sending a third request to the primary content management system for the second metadata associated with the content;
returning the first response, including the second metadata to the remote client transfer module;
receiving the second request for the current version of the content; obtaining the current version of the content from the primary content management system; and
returning the current version of the content to the remote client transfer module.
2. The system of claim 1 , wherein the remote client transfer module and the primary content transfer module are deployed in a cloud environment.
3. The system of claim 2 , wherein the first metadata and second metadata include metadata used by the primary content management system for managing the content.
4. The system of claim 1 , wherein the primary content management system includes a primary content server and a repository server, the primary content server storing metadata for managed content and the repository server storing managed content.
5. The system of claim 1 , wherein the remote client transfer module is further configured for:
receiving a fourth request to save content from the user,
updating metadata associated with the saved content in the data store;
updating the content in the cache with saved content;
sending a second response to the user indicating the content has been saved; and
subsequently to sending the second response to the user, sending a fifth request to the primary content management system to save the saved content at the primary content management system.
6. The system of claim 1 , wherein the first request and second request are included in a single request.
7. The system of claim 1 , wherein the first response, includes the second metadata and the current version of the content.
8. A method for remote caching, comprising:
providing a cache and a data store for storing metadata corresponding to content stored in the cache, where the content in cache comprises content managed by a primary content management system:
providing a remote client transfer module for the steps of:
receiving a first request to access content, wherein the first request is associated with a user;
accessing the data store to determine if first metadata associated with the requested content is stored in the data store;
sending a first request to a primary content transfer module associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store;
receiving a first response from the primary content transfer module including second metadata;
comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;
if the version of the content stored in the cache is the current version, providing the content in the cache in response to the first request;
if the version of the content stored in the cache is not the current version sending a second request for the current version of the content to the primary content transfer module;
receiving the current version of the content;
storing the current version of the content in the cache; and
providing the current version of the content in response to the first request; and
providing the primary content transfer module for the steps of:
receiving the first request associated with the content from the remote client transfer module;
sending a third request to the primary content management system for the second metadata associated with the content;
returning the first response, including the second metadata to the remote client transfer module;
receiving the second request for the current version of the content;
obtaining the current version of the content from the primary content management system; and
returning the current version of the content to the remote client transfer module.
9. The method of claim 8 , wherein the remote client transfer module and the primary content transfer module are deployed in a cloud environment.
10. The method of claim 9 , wherein the first metadata and second metadata include metadata used by the primary content management system for managing the content.
11. The method of claim 8 , wherein the primary content management system includes a primary content server and a repository server, the primary content server storing metadata for managed content and the repository server storing managed content.
12. The method of claim 8 , wherein the remote client transfer module is further configured for:
receiving a fourth request to save content from the user,
updating metadata associated with the saved content in the data store;
updating the content in the cache with saved content;
sending a second response to the user indicating the content has been saved; and
subsequently to sending the second response to the user, sending a fifth request to the primary content management system to save the saved content at the primary content management system.
13. The method of claim 8 , wherein the first request and second request are included in a single request.
14. The method of claim 8 , wherein the first response, includes the second metadata and the current version of the content.
15. A non-transitory computer readable medium, comprising instructions for implementing remote caching in a remote cache system including a cache and a data store for storing metadata corresponding to content stored in the cache, where the content in cache is managed by a primary content management system, the instructions for implementing a remote client transfer module and a primary content transfer module, and
at the remote client transfer module:
receiving a first request to access content, wherein the first request is associated with a user;
accessing the data store to determine if first metadata associated with the requested content is stored in the data store;
sending a first request to a primary content transfer module associated with the primary content management system based on the determination if first metadata associated with the requested content is stored in the data store;
receiving a first response from the primary content transfer module including second metadata;
comparing the first metadata to the second metadata to determine if a version of the content stored in the cache is a current version of the content;
if the version of the content stored in the cache is the current version, providing the content in the cache in response to the first request;
if the version of the content stored in the cache is not the current version sending a second request for the current version of the content to the primary content transfer module;
receiving the current version of the content;
storing the current version of the content in the cache; and
providing the current version of the content in response to the first request; and
at the primary content transfer module:
receiving the first request associated with the content from the remote client transfer module;
sending a third request to the primary content management system for the second metadata associated with the content;
returning the first response, including the second metadata to the remote client transfer module;
receiving the second request for the current version of the content;
obtaining the current version of the content from the primary content management system; and
returning the current version of the content to the remote client transfer module.
16. The non-transitory computer readable media of claim 15 , wherein the remote client transfer module and the primary content transfer module are deployed in a cloud environment.
17. The non-transitory computer readable media of claim 16 , wherein the first metadata and second metadata include metadata used by the primary content management system for managing the content.
18. The non-transitory computer readable media of claim 15 , wherein the primary content management system includes a primary content server and a repository server, the primary content server storing metadata for managed content and the repository server storing managed content.
19. The non-transitory computer readable media of claim 15 , wherein the remote client transfer module is further configured for:
receiving a fourth request to save content from the user,
updating metadata associated with the saved content in the data store;
updating the content in the cache with saved content;
sending a second response to the user indicating the content has been saved; and
subsequently to sending the second response to the user, sending a fifth request to the primary content management system to save the saved content at the primary content management system.
20. The non-transitory computer readable media of claim 15 , wherein the first request and second request are included in a single request.
21. The non-transitory computer readable media of claim 15 , wherein the first response, includes the second metadata and the current version of the content.