XSLT vs ASP.NET MVC framework

Question

Hello, I am in the process of building a very scalable website. I am to the point where I must choose between XSLT and using the asp.net MVC framework and the helper functions. My data is already in XMl format and it will stayy that way. The reason my data is in XML format is because it will be much easier to make changes and I will only need to make only one database query.

I am using asp.net mvc 2 and wondering which approach will be the least resource intensive. I will get many many page views in a minute. if I go asp.net mvc way I will be forced to use linq to xml and if I go xslt way I will just throw xslt the xml and it will transform it.

Answer 1

ASP.NET MVC is not likely to be a barrier to achieving high throughput. ASP.NET MVC does not force you to use LINQ to XML.

Answer 2

You can use ASP.NET MVC with an XSLT view engine.

Answer 3

Its hard to tell with the amount of info you are providing.

Unless you need 0 server side processing, I'd still use asp.net MVC, regardless of the decision to use xslt or not. The only scenario I see asp.net MVC out of the picture, is if it were pure static data and you pre-process all the files to Html files.

There are various factors and options involved. Like @Larsenal said, you are not forced to use linq to xml, and you are also not forced to use return a view in the controller actions / and if you do you have a lot of options in the view engine you use.

Answer 4

Implementing views with XSLT may give you more flexibility and, depending on your background and expertise, such design decision may result in easier, faster to develop and more maintainable implementation.

This would be particularly handy if your models are (represented as) XML documents.