Vertical partitioning was a relatively easy and very impactful scaling lever that bought us significant runway quickly. It was also a stepping stone on the path to horizontal sharding. Figma’s database stack has grown almost 100x since 2020. This is a good problem to have because it means our business is expanding, but it also poses some tricky technical challenges. Over the past four years, we’ve made a significant effort to stay ahead of the curve and avoid potential growing pains.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Tim Liang
Infrastructure | Figma Blog
Engineering Manager Alice Ching discusses the parallels between developing gaming interfaces and building Figma and FigJam, and why our tech stack is more similar to a game engine’s tech stack than a web stack.
Improving Performance with Incremental Frame Loading
When we first built our prototyping features, we had one goal: Allow users to create interactive flows in Figma. From a technical perspective, we built a simple loading strategy to match. We’d load the entire document containing the prototype into memory before displaying the starting screen. Mobile devices (especially iPhones) tend to have less memory than desktop devices, and the operating system would often kill our process instead of expanding our application’s memory budget.
The growing pains of database architecture
In 2020, Figma’s infrastructure hit some growing pains due to a combination of new features, preparing to launch a second product, and more users (database traffic grows approximately 3x annually). We knew that the infrastructure that supported Figma in the early years wouldn’t be able to scale to meet our demands.
How do patients with systemic autoimmune rheumatic disease perceive the use of their medications: a systematic review and thematic synthesis of qualitative research
Characteristics of studies included in the systematic review identified 7392 articles after the removal of duplicates, with 197 forwarded for full-text review. Of note as one of our aims was to update the prior systematic review of patient experiences with SLE [ ] but with a focus on medication use, we only included studies in SLE published 2013 and onwards. In the end, 18 studies met all inclusion criteria for our systematic review (Table ).
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Tim
Contact Tim, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack