Rather than "joins don't scale" it's more like "bad data design don't scale"
Every few years I get the urge to create a RDBMS API that only allows data design using functional dependencies and defined types and possibly rules, i.e. only lets devs do "logical design". Usually happens when I discover some project dependent on EAVIL or giant master table syndrome.
I've got a legion of cynical jokes about "emergent data design" and "Plato's Cave Shadows ERD", HHOS.
wouldn't this be an issue no matter what you're using?
I'm not sure what you mean by joins scale with table size? There are few times you'd join more than say 5 or 6 tables.
This is only true in new tech where data relationship isn't complicated. Any stored procedure in bank would contain joins with no fewer than that number of tables.
The most I saw was "only" 10 though.