SOAP vs REST, which one do you prefer working with ?
thstart: I can tell this after 5 years and 20+ Data Quality web services created for actual users paying actual $'s.Create separate SOAP, XML, REST services on different http addresses. That way you cover 99% of users. Different http addresses allows you to scale via different functionally isolated servers.SOAP is good for computer to computer interface using tools. Good for moderate to complex web services needing a batch processing of many records in Request/Response. Tools help with complex XML structure you get Request/Response Intellisense under .NET. You can use code generators for quick development.REST is good for a manual occasional use, good for quick test and simple single record web services not requiring a batch mode. You can look at the XML response in the browser.XML is a matter of preference and those who got familiar with pre-SOAP. You don't get Request/Response Intellisense. Using XML DOM will slow down processing - you can compose the XML quickly if doing it with string operations. Do not have any advantage over SOAP.Bottom line for our customers - early days XML pre-SOAP just created their interface and forgot it. It just works. When SOAP came the tools made possible quick development. They created it and forgot it. It works fine for them. For quick assessment new customers are using REST. Get a feeling with manual test via the browser. They can see the XML response right away in the browser. When they need multiple Request Records they usually go with SOAP. That way we are covering all bases.