RESTful Web Services vs. SOAP
{"Image DocumentName": "RESTful Web Services vs. SOAP", "Image ImageDescription": "Resource based. Lighter weight. Can use JSON or XML. Contract via documentation. Procedural. Contains more details. Uses XML. Contract via WSDL. When to use SOAP. Intranet applications \u2013 More mature tooling. B2B applications \u2013 Strong contract. Exposing existing applications. When to use REST. Cloud-based and mobile applications. Creating highly scalable stateless applications. For Progress, the decision to add support for REST Web services in OpenEdge was made based on industry trends. For example, REST is the most common way to make Web service calls to cloud based applications. The obvious question is why has REST become the protocol of choice when sending and receiving data be between clients and cloud based services. One answer is low overhead and simplicity. Just to focus on a few areas \u2026. The SOAP protocol provides an interface that can be though of as procedural and utilizes XML to send and receive information. Data types can be defined in SOAP indicating how to interpret the data. REST, on the other hand, - is resource based, relying in a URI to locate a resource. OpenEdge REST utilizes - the JSON format to transmit data. JSON uses name and value pairs for all data. This simpler protocol - reduces the amount of data that needs to be sent over the wire, resulting in improved network performance. Note: The difference: SOAP is transport neutral, while REST is tied tightly to HTTP. SOAP is only XML, and REST can be any media type. SOAP uses formal interface definitions (WSDL) while REST does not (WADL is not enough yet to qualify) The choice: Use SOAP for B2B where an agreed contract (WSDL) is versioned and must be met by all parties. Use REST where agreement is less firm between clients and the provider.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}