A Qualitative Study of Application-level Caching
Jhonny Mertz, Ingrid Nunes

TL;DR
This study investigates how developers implement application-level caching in web applications, revealing challenges and providing guidelines and patterns to improve design, implementation, and maintenance for better performance and scalability.
Contribution
It offers a qualitative analysis of developer practices in caching, deriving practical guidelines and patterns to assist in designing and maintaining application-level caching.
Findings
Developers face challenges in manual caching implementation.
Guidelines and patterns help improve caching practices.
Caching is crucial for scalability and performance.
Abstract
Latency and cost of Internet-based services are encouraging the use of application-level caching to continue satisfying users' demands, and improve the scalability and availability of origin servers. Despite its popularity, this level of caching involves the manual implementation by developers and is typically addressed in an ad-hoc way, given that it depends on specific details of the application. As a result, application-level caching is a time-consuming and error-prone task, becoming a common source of bugs. Furthermore, it forces application developers to reason about a crosscutting concern, which is unrelated to the application business logic. In this paper, we present the results of a qualitative study of how developers handle caching logic in their web applications, which involved the investigation of ten software projects with different characteristics. The study we designed is…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
