3

Is it bad, from a scalability perspective, to use an ASPX page as though it were an ASMX service?

Specifically, we've set up an ASPX page whose code behind simply looks at what data was posted to it, does some operations, and Response.Writes the results. jQuery treats the results like json, and all is good; it works.

My question is, will this solution suffer from a scalability perspective, compared to ASMX or WCF? I know these technologies have all sorts of features to make the code more simple, but I'm merely asking about performance and scalability.

Adam Rackis
  • 82,527
  • 56
  • 270
  • 393

2 Answers2

0

you should need to Visit this links WCF VS ASMX WCF VS ASMX

Jignesh.Raj
  • 5,776
  • 4
  • 27
  • 56
  • This really just talks about the greater power and configurability that WCF offers. I'm asking whether using an ASPX page as an ad hoc web service will cause scalability problems down the road. – Adam Rackis May 21 '13 at 04:41
0

You already have a good answer but, if you want results like json, WCF supports rest services which are similar to calling aspx pages. You can get detailed information from here.

Selcuk S.
  • 661
  • 2
  • 9
  • 19
  • Again, I already know that WCF provides many features that asmx and aspx lack. I'm asking about whether there are any scalability problems with using a single aspx page to act, essentially, as an ad hoc web service. – Adam Rackis May 21 '13 at 15:56