Document Controls
For Application Development Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
May 24, 2004 Selecting A Middle-Tier Cache ArchitectureTechnology Options For Higher Scalabilityby Carl Zetie with Randy Heffner, Kimberly Q. Dowling |
Average: 9
(2 ratings)
|
This is an excerpt
Executive Summary
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.
TABLE OF CONTENTS
- Caching In The Middle-Tier Can Improve Scalability
- Technology Landscape
RECOMMENDATIONS
- Begin By Analyzing The Application, Not The Vendors
- Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
