Discussing service oriented architectures with a number of developers recently, made me realize that there is real confusion about how an ASP.NET XML Web Service should be implemented architecturally.
Many appeared to think that somehow business logic should be implemented in the Web Service, which would be serviced by the data tier, with one or more presentation layers consuming the service.
Why think this?
The answer is that that's what most articles and examples tend to show. Most show business logic being performed in a service method. Admittedly, it is often shown that way in order to show how to consume an XML Web Service, but does soat the cost of the bigger picture.
Surely examples should more correctly show a Web Service acting as an interface to business logic. Business logic that is serviced by the data tier and ifapplicable, enterprise services. Business logic which is generally represented directly through a presentation layer.