Architecture Critique: SQL Server FOR XML into XSLT for Rich HTML Interface

Question

Can I get some constructive feedback about the following architecture?

Simplified Architecture Summary:

Return XML from your SQL Server (using FOR XML) and pass it straight into a XSL transform to produce a rich HTML web site.

What are the pro’s and con’s of such a system when compared with a conventional 3-tier ASP.NET architecture?

Answer 1

Two cons.

1. Data manipulation with C# or VB.net becomes harder because you don't have classes with properties (code intellisense) but xml-documents.

2. There are built in asp.net controls for data entry validation (both client side and server side). You can't use them if you use XSLT to produce your HTML-page.

Answer 2

We have done something like this. And it works for very simple pages. But as soon as you would like to include some client side javascript and similar, you are doomed.

The generated output is hidden in the XSLT stylesheets and it is very hard to read, maintain and fix bugs.

Testing can be done, but also with much more effort than before.

The MVC pattern and similar is much better suited for such a scenario.

Answer 3

I've done something similar in a project. I find the architecture very clean and scalable, but I would only advise you to use it if you happen to have lots of XSLT expertise in house.

We have a few XSLT templates, and a generic c# class that performs the transformation, using XSLT parameters. We get very good performance but, for new developers, the app can be hard to maintain.

Answer 4

One pro:

1. You can make XSLT-templates that produces HTML for the browser or XAML for WPF/Silverlight.