What about fixing the DB access and making all operations async? The nop team should look at this topic
and take action.
Also, the architecture needs to be reviewed. It is not normal having controllers with 20 services injected in the constructor and in their turn, the services having 20 more services injected in their constructors. Also, many controller actions and service methods are extremely long.
The performance is bad and customization and maintenance is difficult. Fixing this should be top priority in my opinion.
Sorry to be so critical, I could also write many good things about nopCommerce.
I'm totally agree.
Nop architecture needs a good review to better scale in cloud environments but also on local servers.
I'm also thinking about a 2nd level cache layer, something like Umbraco 8 'cache neuve'.
.net core could also help but, in my opinion, should be done after the architecture review.