HOW FIGMA'S DATABASES TEAM LIVED TO TELL THE SCALE

Summary from the TLDR Web Dev newsletter

Figma's database team had to deal with hypergrowth that was starting to outpace their database's capacity. To address this, they first focused on vertical partitioning, which bought them time but was not a long-term solution. They then embarked on a complex nine-month project to implement horizontal sharding, tailoring their approach to Figma's specific needs. To manage their horizontally sharded databases, they built a service in Golang to support load-shedding, transaction support, database topology management, and more.