""Scalability and reliability gaps in our Redis platform were a growing threat to Figma's site availability." Kevin Lin, Software Engineer, Figma."
"The symptoms that motivated the project were familiar to anyone who has run Redis at scale. Connection volumes were creeping towards hard limits. Rapid scale-ups of client services produced thundering herds of new connection requests, saturating Redis I/O and degrading availability.""
"Lin notes that existing solutions shipped with 'rudimentary RPC servers that were not capable of extracting' the necessary performance and reliability needed for Figma's operations."
Figma created FigCache, an in-house Redis proxy service, to address scalability and reliability issues that threatened site availability. This service has been operational since the second half of 2025, achieving six nines of uptime. The development followed a previous rearchitecture of their Postgres stack with DBProxy. The team faced challenges with connection volumes and independent client libraries, leading to the decision to build a custom solution rather than using existing open-source proxies, which lacked necessary capabilities.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]