Architecture Roadmap: MVC

When building anything for the web, you have to become proficient at frontend technologies. Ultimately this means HTML, CSS, and Javascript, but rarely are websites built with just those three things anymore (certainly not anything data-driven, which is to say, basically everything). What’s more likely is that a framework is used that makes it easy to render those things out to a user’s browser. In the .NET world, this usually comes down to a decision between two things: ASP.NET Webforms or ASP.NET MVC.


Perception is Everything

Similar to our new responsive storefront, one of the biggest, and loudest, questions partners and customers have asked us is “When are you going to MVC?”. You see, even though webforms isn’t going anywhere and is still a viable frontend framework, it’s generally considered “old and dying”. The perception is that if you haven’t moved from webforms to MVC, then you’re wrong. In other words, keep up with the times or customers will look for alternatives.


The Old College Try

We actually thought we had this nailed down a few releases ago, but we scuttled it late in its cycle because the quality and performance wasn’t where it needed to be. Many factors contributed to that decision, but it should be known the *least* determining factor was MVC itself.

Having put that behind us, we’ve made a number of architectural improvements since then that allowed us to revisit MVC and approach it from an entirely different angle. The result is nothing short of staggering. The design is thin, clean, and very easy to maintain and extend, and because all the real work happens behind our API, performance is through the roof.


Cross It Off the List

From a roadmap perspective, being able to check MVC off the list is a major accomplishment. It not only provides a vastly improved out-of-box experience for our customers and partners, but also provides them an exact blueprint for how they can implement their own ecommerce storefronts.