Conclusion
The ability to store in memory chunks of frequently accessed data becomes a winning factor in the building of scalable Web applications that handle significant volumes of data. Instead of continuously connecting to the database server, locking records, and consuming one of the available connection channels, you can simply read the results needed from some block of memory. This scenario delineates caching as an asset for any application. Well, not just any, as we discussed—but certainly for many.
Caching is rather a double-edged sword, and if abused or misused, it can easily morph into an insidious weakness. This typically happens when the quantity of memory-held information grows uncontrolled and beyond a reasonable threshold. Aside ...
Get Programming Microsoft® ASP.NET 3.5 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
