Something I learned about writing robust code is that scalability needs to be tested up-front. Test with 0, 1, and
many where the latter is tens of millions, not just ten.
I've seen production databases that had 40,000 tables for valid reasons.
I've personally deployed an app that needed 80,000 security groups in a single LDAP domain, just for it. I can't remember what the total group number of groups across everything was, but it was a decent chunk of a million.
Making something like Git, or a file system, or a package manager? Test what happens with millions of objects! Try billions and see where your app breaks. Fix the issues even if you never think anyone will trigger them.
It's not about scaling to some arbitrary number, it's about scaling, period.
I've seen production databases that had 40,000 tables for valid reasons.
I've personally deployed an app that needed 80,000 security groups in a single LDAP domain, just for it. I can't remember what the total group number of groups across everything was, but it was a decent chunk of a million.
Making something like Git, or a file system, or a package manager? Test what happens with millions of objects! Try billions and see where your app breaks. Fix the issues even if you never think anyone will trigger them.
It's not about scaling to some arbitrary number, it's about scaling, period.