adam121 - Fotolia

Get started Bring yourself up to speed with our introductory content.

Making REST, SOAP, API mashup choices

Expert Amy Reichert discusses API mashups, REST and SOAP.

When making decisions about application program interface (API) development and uses, developers have been known to debate the comparative values of the REST and SOAP standard communication protocols. In this podcast, veteran software-development consultant Amy Reichert lays out the arguments for and against using REST and SOAP in various use cases. She also gives advice about the best uses for API mashups and the WebSocket protocol.

What lies behind REST’s appeal as a Web service is its simplicity, exemplified by a lower learning curve than that of SOAP, according to Reichert. REST carries a lighter messaging layer and services that are easier to integrate with existing websites, the reason for the latter being that REST services are exposed with XML, a markup language that’s easily mated with standard HTML webpages.

SOAP shines in complex API settings because it has built-in context and state. Supporting complex actions with REST would require writing code in the application layer that already exists in SOAP, Reichert says.

Take a listen to this podcast and find out more about API settings, REST and SOAP.

Next Steps

Explore API technology and trends

This was last published in September 2014

Dig Deeper on API management strategy

PRO+

Content

Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide.com

SearchWinDevelopment

DevOpsAgenda

Close