Re:How Figma's databases team lived to tell the scale
by eatonphil on Thursday March 14, 2024 @02:41PM
(#39707482)
I imagine it only gets you so far. What do you do about customers like Walmart or Oracle? Hundreds, if not thousands, of users all leaving hundreds of comments on Figma files every day. If you want good latency without giving up strong consistency (which the article says they want) you'll need to keep sharding.
[ Parent
| on HN ]
Re:How Figma's databases team lived to tell the scale
by jeremyjh on Thursday March 14, 2024 @04:24PM
(#39708541)
They were running their whole business on one RDS instance 4 years ago. Do you think they now have one customer larger than all their customers combined 4 years ago?
Re:How Figma's databases team lived to tell the scale
by eatonphil on Thursday March 14, 2024 @04:27PM
(#39708565)
> Figma’s database stack has grown almost 100x since 2020
The first sentence from the article seems to suggest its possible?
Re:How Figma's databases team lived to tell the scale
by willsmith72 on Thursday March 14, 2024 @03:04PM
(#39707726)
A single db can handle that load easily
Re:How Figma's databases team lived to tell the scale
by paulryanrogers on Thursday March 14, 2024 @08:48PM
(#39710881)
Do you mean an RDBMS running on a single, big-iron, bare-metal server?
Re:How Figma's databases team lived to tell the scale
by infecto on Thursday March 14, 2024 @05:20PM
(#39709113)
I bet it gets you further than you imagine. Entirely depends on the backend services and what they touch but in this scenario you would be deploying/scaling that service based on the customer seat size. I suspect that even for large enterprise customers, the users actively touching Figma are not reaching he thousands but I am happy to be wrong.
After all, Stackoverflow is running off of a handful of machines.