nopCommerce with vNext ?

Hello,

I'm very new to this forum.So I do have 2 questions.

Q 1 : I saw, you're using ASP.net MVC 5 and EF 6 with latest Nop version (3.4).But I couldn't find the usage of "async API" with it.I mean EF async and Controller async features. Why's that ? Do you have any plan to use those features with your future releases ?

Q 2 : What's your future plan for the Microsoft's next major change vNext ? Do you have any plan for it with Nop ?


I hope you'll give a feedback for it.Thanks in advance.

1. No. Where exactly do you suggest do you use (and why)?
2. nopCommerce always uses latest technologies. But let's wait until Visual Studio 14 RTM is released

Hi,

Thanks a lot for your feedback.

1. No. Where exactly do you suggest do you use (and why)?

If you see the latest Identity implementation,it's totally developed by using Async apis. B'cos it'll give more responsiveness to the UI. Means will have better performance.And if you need to cancel some time consuming operations (may be clicked accidentally or so) then user will have the opportunity to do so if we use Async with our actions.Please check the below mentioned url where it explains using simple example.

http://stackoverflow.com/questions/19087513/what-is-the-advantage-of-using-async-with-mvc5

In general, we can use asynchronous methods for the following scenarios :

You're calling services that can be consumed through asynchronous methods, and you're using .NET 4.5 or higher.

The operations are network-bound or I/O-bound instead of CPU-bound.

Parallelism is more important than simplicity of code.

You want to provide a mechanism that lets users cancel a long-running request.

When the benefit of switching threads out weights the cost of the context switch. In general, you should make a method asynchronous if the synchronous method waits on the ASP.NET request thread while doing no work.  By making the call asynchronous,  the ASP.NET request thread is not stalled doing no work while it waits for the web service request to complete.

Testing shows that the blocking operations are a bottleneck in site performance and that IIS can service more requests by using asynchronous methods for these blocking calls.

I got it from here : http://www.asp.net/mvc/tutorials/mvc-4/using-asynchronous-methods-in-aspnet-mvc-4

2. nopCommerce always uses latest technologies. But let's wait until Visual Studio 14 RTM is released

Yes.I agreed with you. I'm happy to hear that nop always uses latest technologies.Which is Great and will have very bright future if you'll do so.

Using async apis would do absolutely nothing to improve responsiveness, the only place it might help is if you had an ajax heavy site. Nopcommerce uses a request response paradigm, and the processing NopCommerce does on request could not be improved using async calls.

Hi timmit,

Please read this article http://www.asp.net/mvc/tutorials/mvc-4/using-asynchronous-methods-in-aspnet-mvc-4,Then you'll have better understanding about the latest Async APIs. This is not for the ajax heavy sites.This is for the request response paradigm sites.Ajax by default async. So there is nothing to do with the Microsoft's Asyn APIs.Please read the above article.

Hi, timmit is correct. Using async wouldn't have any effect regarding the responsiveness of the site. If a request takes 1 second to process, it will take exactly the same time using async.

Also, there is no way an async operation on ASP.NET can be cancelled by the user.

What is really interesting about async in an application like nopCommerce is that for a request that takes 1 second, probably 80% of this time nop is waiting for a response from the database. This means having the server wasting resources just for waiting. If we use the async features of EF, the ASP.NET threads are freed while waiting meaning that the same server will be able to attend many more requests at the same time.