Not if your company goes bankrupt trying to prematurely upgrade the architecture, which is usually a huge undertaking. I think that's the entire point of the article, the guy who wrote it is clearly using a startup POV.
It makes sense to build a cheap and dirty system to start. Especially if you want to build it then inject loads of cash when it takes off. But it is still a cheap and dirty system.
Too many people do build like this initially but are not willing to pay to fix the mess when it starts to get hard to add new features.
Too many people do build like this initially but are not willing to pay to fix the mess when it starts to get hard to add new features.