Community discussion forum

REST and .NET 3.5 Part 1 - why REST based services?

This is a comment thread discussing REST and .NET 3.5 Part 1 - why REST based services?
  • 10 years ago

    This thread is for discussions of REST and .NET 3.5 Part 1 - why REST based services?.

  • 1 year ago
    Erm, except Amazon exposes all of their APIs via SOAP. It's not really and apples-to-apples comparison either, because both Google and Yahoo cite ease of use/low barrier to entry as being a talking point on why they're not or are no longer supporting SOAP. The fact is, all the APIs that I know of that they're currently exposing are really targeting presentation layer logic and mashups. SOAP really wasn't designed to be as lightweight or included in client-side logic; by comparison, Amazon's services really target enterprise developers, and as such many more people wind up using SOAP to access their services than used it with Google's API when they were still offering the service. Google and Yahoo offer maps, search, and the like, while Amazon offers asynchronous queues (who uses queues for a lightweight mashup?), fault-tolerant storage, and scalable servers. I agree with most of what you're saying, just wanted to point that out; most sites aren't switching to REST because its merits, but because its lower learning curve draws in a larger potential developer base.
  • 1 year ago
    Is anyone interested in working on Windows Live Social Networking site? This is all done in C# and ASP.Net with a little Ajax. -Ryan Phillips engineerfinder@live.com

Post a reply

Enter your message below

Sign in or Join us (it's free).

We'd love to hear what you think! Submit ideas or give us feedback