Wat...

This article reads like a jumbled mess of ideas. But, the above is a total wat...

And it also assumes that your backend doesn't have to consume and tie together several resources or that you need a caching layer and so many other naive assumptions - and I'm not even addressing the security implications.

Take this article with a heavy cup of salt.

To me it just reads like something someone would write because they want full control and does't like working with and/or being dependant on other people/teams.

if you do manage to get to the interview process, ask about the job you are being interviewed for so you can get a better understanding. a job interview is a conversation, so it goes both ways. try to find out why they are looking for a new employee. for example, they may be looking for a system administrator to do sysadmin tasks, but if you ask further, they might tell you that they are in the process of trying to scale their systems, at which point you can talk about your past experience or what ways your might go about developing a scalable architecture. make yourself relevant.

all too often, candidates just come in and sit quietly, waiting for the interviewer to ask them question after question, trying to pull information out of them and then it simply becomes checklist of questions to tick off (while looking at your watch) before thanking the interviewee and showing them the way out.