nopCommerce 4.00 roadmap and estimated release date. Let's discuss

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 won't list all highlight/enterprise features here as we always did it before. But just because there are really a lot of them. Find them here

Please also find a complete list of all existing work items for this version here.

Your thoughts and suggestions are more than welcome!

Estimate release time - October-November 2017 (7-8 months)

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 agree.  Right now we run our databases in Azure (Data Service) and run S2 with geo-replication.  Its $75 per month just for the database and after replication, its $150 per nop database. Web Server costs are all on top of that.  We tried lower plans on Azure, but the DTU just doesn't cut it for a site of any size.
From a "business value" perspective, the issues discussed in this topic are more important than jumping onto .net core.  If the goal of nopCommerce is to have dramatic growth in the community, then critical business needs like architecture optimization to alleviate high hosting costs need to be solved.  If the goal of nopCommerce is to push the latest in technology, then .net core migration makes sense.
There is a balance to be struck I believe... I think you should just have 2 work items for 4.0
1.  The planned .net core does have many attractive benefits, especially around handling web api, etc. and it could be leveraged for performance optimization.
2.  Architecture Optimization - Including async methods, etc.

Instead of a 8 month release window, release 4.0 when the above 2 items are ready.

All other features listed seem secondary and could wait until 4.1 (even price per currency work item).  If we optimize the plumbing, remove the barriers/high costs of handling larger sites more people will adopt the platform faster.

Please don't take the above statements the wrong way. I love nopCommerce and think the team has done a fantastic job.  I just want to see the product grow in the right direction.
Also: codeplex had a nice vote option...now that were in git, we need something similar to vote to help drive future road maps.

Thanks