Often the question of SQL vs NoSQL will come up.\nI\'ve been reading pros and cons, and most of them make sense to me. But there is one that bothers me.\n\nQuoting from one of those articles:\n> Scalability: In most common situations, SQL databases are vertically scalable, i.e., by increasing the horsepower (higher Memory, CPU, etc.) of the hardware, which can get very expensive. It is possible to scale a relational database across multiple servers, but this is a challenging and time-consuming process.\n\nNo one will tell you to design something that "does not scale", so it would seem that scale is a blocking factor to always stay away from relatinal databases.\nHowever, I would find it hard to believe that any self respecting database company will sell you a product that does not scale.\n\nIs this limiting factor of scale real? \nI\'d love if you have some inisghts or good reading on the subject.\nI don\'t want to look like a fool in an interview when saying "we need scale therefore let\'s not choose relational".

Often the question of SQL vs NoSQL will come up.\nI\'ve been reading pros and cons, and most of them make sense to me. But there is one that bothers me.\n\nQuot