Generic Architecture for Caching Table Data: Keeping It Real (and Small) - Conclusion

(Page 4 of 4 )

We have shown some techniques that can be used to manage the cache size and refresh records in the cache.  If we add this to the Caching Architecture we get the following:

1. Create a cache.
   
2. Create a procedure to empty the cache.
   
3. Create a switch for the cache, a public procedure to “set” the switch and a function to verify what the switch is set to.
   
4. Create a read, write and query procedure.
   
5. Create Procedures to refresh the cache content.
   
6. Create a global variable to store the maximum cache size, a public procedure to “set” the size and a function to verify what the size is set to.
   
7. Create a data retrieval function.
   
8. Create a log procedure.

In the next part of the series we will add procedures that monitor the effectiveness of our cache.

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

Comments On: Generic Architecture for Caching Table Data: Keeping It Real (and Small)

· Hi,Third article in the (4 part) series, hope you enjoy it. Feel free to pass...   >>> Post your comment now!