Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb Service VS. Aspx Pages: Pros and Cons
    text
    copied!<p>We develop an ASP.Net web application that is hosted on an internal network. Currently, we have some ASPX pages that handle web requests from the client side and interact with our servers. We are starting development on our next major application version, and we are deciding on the architecture.</p> <p>What are the differences between using ASPX pages to handle http requests as compared to using a full blown Web Service (which would most likely be a WCF Service)?</p> <p>In researching this issue, I have come across a few related posts that have been moderately helpful, seen <a href="https://stackoverflow.com/questions/1845461/can-a-server-page-jsp-aspx-be-used-as-web-service">here</a> and <a href="https://stackoverflow.com/questions/4123764/wcf-service-as-a-replacement-for-aspx-service">here</a>. My understanding of some of the key differences are as follows:</p> <ol> <li>ASPX pages are limited in the kinds of requests they can receive. They are strictly HTTP whereas a WCF service can have multiple endpoints to service a variety of protocols (HTTP, TCP, etc).</li> <li>WCF Services are more concretely defined due to ServiceContracts. This means that if a project makes a reference to the service, they know exactly what to expect in terms of methods, usage and documentation. An ASPX page is more of a free for all in terms of methods contained and requests accepted.</li> </ol> <p>However, based on these concepts, my issues are as follows:</p> <ol> <li>The ability to support different protocols is a great feature in terms of future proofing and compatibility, but what real benefit are we seeing if we are currently <em>only</em> using it to interact via HTTP?</li> <li>In line with my previous argument, if we are only interacting with the service over a web, do any of those points really make any difference? An http request doesn't care about any of those finer details or contractual guarantees so long as the method it calls "just works".</li> </ol> <p>Is there anything I am missing? Any key benefit to using a service? Personally, I support the Web Service architecture. I like the idea of having a flexible and well defined system that can support future development. What I am basically looking to get out of this is a way to go to a coworker and say "This should be a service for x y z reasons and we could see a b c improvements for doing so".</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload