Talking about an architectural pattern without specifying its applicability or limitations or context is just completely wrong. In architecture it's not option

Talking about an architectural pattern without specifying its applicability or limitations or context is just completely wrong. In architecture it's not optional to proceed as follows: 1. describe a problem, 2. describe a solution to the problem They don't do that. This is a classic mistake: describing a solution and looking for a problem to solve. Don't do that! Furthermore, MVC is used because it's widely applicable to a bunch of problems and contexts - with its pros and cons, clearly. It's actually a very rare thing for a pattern to have such a large sphere of applicability. So, no, you don't throw it away just like that. It doesn't make any sense. Sure, there are other patterns that work better in some very specific context. CQRS is an excellent pattern for building NoSQL databases for example. That doesn't mean it should be applied to any random problem!