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

3 years ago
fcastells wrote:
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.
3 years ago
Please implement angular 2 or react in admin panel to make admin panel faster.
3 years ago
a.m. wrote:
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)

Great step of Nop to move to ASP.Net Core!! The work items included in the roadmap are great.

SUGGESTION: In regard to the work items in the roadmap, for us as developers, for planning purposes, it is very important to know with a good certainty which work items will actually be done, specially those labeled as "enterprise features". It happens very often that the number work items announced at the beginning is later substantially reduced/posponed. Could you add a tag in each work item which indicates the probability that it will be done (e.g. "Sure", "Very Probably", "Maybe")?
3 years ago
Improve Attribute Combinations generations

At the moment there are to options: add an attribute combination manually one by one, or generate all the possible combinations. Imagine that we have 10 colors and 20 sizes in our attributes, but we want to add shoes with 3 colors and 10 sizes, is really annoying to add all single combinations one by one or generate all possible colors/sizes combinations and than delete the ones that you don't need.
The best way is to generate the all the combinations but only with the attributes you really need, for
example from colors you choose: red, yellow, black and from size 5-15. Something like prestashop already does:



try it by yourself guys:
http://demo.prestashop.com/

https://github.com/nopSolutions/nopCommerce/issues/2243
3 years ago
I agree that updating the infrastructure should be top priority, speed on Azure is an issue! Async everything would help as would cutting down on the number of database calls.

On a separate suggestion it would be nice if the front end was based on a CSS framework to make templating easier.
The obvious one would be bootstrap! Using a grid system just takes so much pain away from page layouts, etc.
3 years ago
exciting times indeed!

is there already a work item to make ACL permissions store based?

tx
3 years ago
ChuckR wrote:
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


I agreed.
3 years ago
Hi Andrei,

I would suggest a new feature - product attribute value description to be added in 4.00 This implementation allows store owners to add Description to checkout/product/specification attribute values.For example this would allow you to show more info to customer about the attribute value option.

https://github.com/nopSolutions/nopCommerce/issues/373
I also created a pull request on github

It would be great if we see it in v4.00

Thanks,
D. Dochev
3 years ago
Please incorporate some Azure deployment and update assistance because this makes my head hurt.
3 years ago
i think we need to add this issues to 4.00 Milestones
https://github.com/nopSolutions/nopCommerce/issues/2280
https://github.com/nopSolutions/nopCommerce/issues/2236
https://github.com/nopSolutions/nopCommerce/issues/2191
https://github.com/nopSolutions/nopCommerce/issues/2282
https://github.com/nopSolutions/nopCommerce/issues/2281
https://github.com/nopSolutions/nopCommerce/issues/2258