asp.net design pattern with angular

i have many years of programming in micro soft platforms like "windows forms","asp.net web forms", "asp.net mvc" , and now "asp.net core" with "entity frame work core" and etc...

In these years we were familiar with the concepts of software architecture are mainly influenced by microsofts point of view (ASP.net design patterns...). But with the advent of new technologies and frameworks such as Angular that has caused front-end layers(tier) are fully separated from back end, i see that with using front-end frameworks like angular, the "ASP.net MVC" architecture is crumbling, because there is no view more needed in back-end!(M-?-C) with this scenario you only need web api as a back end service and in this case i think that i dont need complex separation of concepts and design patterns like n-layer architecture and using fat orms like EF with complex dependencies and complex implementation of unit of work, repository pattern and its generics and other headaches any more.

i simply can use api for back-end and calling my stored procedures from database. in this case i think that even there is no need to microsoft.net and can use other platforms like nodejs, is it right way?

I am concerned about respect the standards and design patterns. should i be looking for another design patterns? how is living in a world without MS concepts? is there solution or practice?