Frontend implementation for ASP.NET MVC?

Question

JavaScript

Welcome all.
At the moment, it is necessary to create a very large web service, highly loaded and operating with a large amount of different data.
What exactly will be :

1. Many users of different statuses (admins, dispatchers, supervisors)
   
2. Working with Yandex.Maps
   
3. Telephony Integration
   
4. Lots of popups, trees, grids
   
5. The interface must be very fast and work in real time
   
6. SPA or not - it doesn't matter
   

As a web service, either ASP.NET MVC or WEB API is seen.
But the problem is with the frontend.
If you take a simple razor, then even with the table it's already plugged in, because it will still have to be built up, stylized and twisted.
If you take razor + a set of controls (such as jqGrid and a bunch of other plugins for popups, trees), then in fact each plugin will have to send jsonResult to each event, which is similar to using angular.
If you take angular, then the range of its UI controls is also not to say that it is rich and beautiful, but you will have to teach it fairly.
Question: which of these options is better in terms of speed / simple development + work efficiency / load? Is there any other good link? And in general, on what front-end are serious web applications based on ASP.NET MVC made?

Answer 1

Good afternoon!
Given the volume of tasks and probably not very long terms for their implementation, it may make sense to give the front-end to a professional. But if this is not possible, then I would prefer the usual Razor.
I'll try to explain why.
1. AngularJS (and others like it), alas, is not familiar to me. Therefore, you need to spend a lot of time studying it and solving problems during its use in the project. And this, in turn, can greatly affect the timing of the project.
2. Use any ready-made controls (ala jQueryUI grids, etc.) - here I would not rush. Whatever one may say, there comes a moment when it is necessary that these controls can do what they want from them, but what they are not adapted for. As a result, the code is overgrown with wild crutches. Besides, in my opinion, the appearance leaves much to be desired... If there comes an understanding that this control will be able to solve the problem, then it can be applied.
3. I would take some normal frontend-framework (Bootstrap, FlatUI, Pure) as the basis of the front-end. Perhaps - even a few (I myself prefer Pure Grid + FlatUI). Styling problems will be much less than if you write everything yourself from scratch.
4. Razor is quite simple if it is used correctly (I mean the correct division into Layout, Partial View, View, if necessary, output caching) - I don’t understand why it scares you so much.
5. As for any pop-up windows, trees, grids - I would prefer special plugins (a separate plugin for windows, a separate one for trees, a separate one for grids). As a rule, you can find very convenient, simple and customizable solutions. In my opinion, it is better to use some specialized tools (which solve only 1 task) than unified ones (which can solve a whole bunch of problems).
It would be great if other experts gave their point of view. It's interesting to see how people solve problems like this...

Answer 2

Well, firstly, if you have a large application under load, there will be a lot of bottlenecks without a backend. DB for example. IMHO - the best solution would be a database - WEB API for returning data (useful if there is something other than a web muzzle) - Angular.