Re:How Figma's databases team lived to tell the scale
by nightpool on Thursday March 14, 2024 @09:38PM
(#39711217)
That's still 2 orders of magnitude smaller than the scale of Figma—they would need to somehow manage millions of Postgres schemas. I don't think it's a realistic possibility
[ Parent
| on HN ]
Re:How Figma's databases team lived to tell the scale
by tharkun__ on Friday March 15, 2024 @01:00PM
(#39717943)
https://news.ycombinator.com/item?id=39711815 Shopify seems to have millions of customers. Granted, they have MySQL and it might not use database schemas and something more MySQL specific. In general though ...
Re:How Figma's databases team lived to tell the scale
by nightpool on Friday March 15, 2024 @02:22PM
(#39719020)
"We can attach a shop_id to all shop-owned tables and have it serve as a sharding key. Moving a shop from one shard to another involves selecting all records from all tables that have the desired shop_id and copying them to another MySQL shard. For this post, it’s helpful to think of each pod as a MySQL shard."
Sounds like this is just normal sharding. Completely different from having a totally separate schema like GP proposes (with that approach you don't use sharding keys at all).
Re:How Figma's databases team lived to tell the scale
by tharkun__ on Friday March 15, 2024 @08:28PM
(#39722136)
I don't see how it follows from that. "Attach" seems very generic.
But I do see now, searching for that part of the info specifically, they mention
Peppy Peppers’ orders can be migrated by running SELECT FROM orders WHERE shop_id = 1 FOR UPDATE on Pod 1’s database
Yeah that's just having the tenant id in the table directly. Oh well!