> you have to avoid using certain features like joins Too bad it is kinda sorta the thing with a RDBM. Relationnal. When you have to work with data which are r

> you have to avoid using certain features like joins Too bad it is kinda sorta the thing with a RDBM. Relationnal. When you have to work with data which are related and don't want to do stupid shit like updating the infos of an author in each of its written article you want SQL. But nothing prevents you from using a NoSQL database on top or even multiple ones. If you have multiple way to use your data, having multiple read or write models is a plus. About scale: rare are the people who can't just add more hardware to the problem.