Executive Summary (This is a document excerpt)

Highly scalable transactional applications often require that access to shared data be distributed across multiple sessions on separate machines. When fetching such data from a shared persistent store (database) and committing changes back to that store become a performance bottleneck, architects turn to caching in the middle tier. By managing data closer to where it is used and propagating changes to where they are needed without constantly returning to the database, architects can improve performance and scalability. However, a middle-tier cache adds significant architectural complexity. Furthermore, there is no single universally agreed upon standard that is best for all caching requirements, making product selection more difficult. For these reasons, the decision to introduce a cache should not be taken lightly. Despite these barriers, a middle-tier cache is an important weapon in the architect's arsenal.

Buy Risk-Free

Download and print PDF immediately. Price: US $499

Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.

Already a Forrester Client?
Log in to read this document.