FaaT: A Transparent Auto-Scaling Cache for Serverless Applications
Not on the map. Why?
Abstract (arXiv)
Function-as-a-Service (FaaS) has become an increasingly popular way for users to deploy their applications without the burden of managing the underlying infrastructure. However, existing FaaS platforms rely on remote storage to maintain state, limiting the set of applications that can be run efficiently. Recent caching work for FaaS platforms has tried to address this problem, but has fallen short: it disregards the widely different characteristics of FaaS applications, does not scale the cache based on data access patterns, or requires changes to applications. To address these limitations, we present FaaT, a transparent auto-scaling distributed cache for serverless applications. Each application gets its own FaaT cache. After a function executes and the application becomes inactive, the cache is unloaded from memory with the application. Upon reloading for the next invocation, FaaT pre-warms the cache with objects likely to be accessed. In addition to traditional compute-based scaling, FaaT scales based on working set and object sizes to manage cache space and I/O bandwidth. We motivate our design with a comprehensive study of data access patterns in a large-scale commercial FaaS provider. We implement FaaT for the provider's production FaaS platform. Our experiments show that FaaT can improve performance by up to 92% (57% on average) for challenging applications, and reduce cost for most users compared to state-of-the-art caching systems, i.e. the cost of having to stand up additional serverful resources.
Key facts. Cited by 3 papers in the map (data through 7 Oct 2026). First posted on arXiv 28 Apr 2021.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2024: 3.
3 papers.