Geek Answers Handbook

Windows Azure + Asp.Net MVC + E-Commerce

I will develop and host an e-commerce site based on Asp.Net MVC4 (with multiple SQL Server jobs).

I think using Azure to stay in the Microsoft world and avoid specialized server management.

The package website, combined with 1 site / 5Go SQL Server Database / 200Go Bandwidth, is very interesting for a price based on 12 months.

But I do not know if this configuration is enough for bandwidth.

What do you think? Have you used Azure with this type of application?

Regards, Guillaume.

+4
source share
3 answers

If you want to develop an e-commerce application, you will have to protect confidential customer data, such as credit cards, addresses, etc. over secure connections ( HTTPS, in many countries this is a legal requirement )., For this reason, you will need SSL support.

Azure Website does not support SSL for custom domains. However, they do support SSL for the DNS name .azurewebsites.net DNS. So if your DNS e-commerce application is, say, my-ecom-app.azurewebsites.net, then this is normal. Otherwise, I would not recommend the Azure Website solution yet (I am sure that SSL support for user domains on the Azure Website will be implemented).

Azure Cloud Services , on the other hand, has full SSL support for user domains.

One of the really good sites for testing Azure features and the development roadmap ScottGu Blog

+3
source

Azure websites do not support SSL, and I really do not know of any successful e-commerce site that does not start SSL, at least for part of the website. If you really want to conduct your e-commerce on Azure today, your only real choice is to run virtual machines for front-end servers and use them for your database or use SQL Azure.

0
source

We developed a platform called Virto Commerce that does just that, the MVC4 website hosted on Azure. It also required SQL work (indexing, payment processing, emptying the basket, etc.), for which we used WorkerRole (instead of WebRole). WorkerRole and WebRole can be combined as part of the same deployment, but it is better to use a different instance for worker roles. In our case, WorkerRole acted as a scheduler for several tasks defined in the database.

However, the problem with WorkerRoles is to make sure they scale well when adding new instances. Thus, the workload must be distributed among multiple instances. This is done using queues and blob locks, where each task is now divided into two, one of which schedules and divides the work, and the second actually picks up the next section and completes it.

Hope this helps!

PS: Virto Commerce is now available as an open source project on codeplex, go to http://virtocommerce.codeplex.com

0
source

More articles:


All Articles