Representational state transfer (REST) is a stateless software architecture that reads webpages containing XML. REST, which some architects view as a simpler alternative to Simple Object Access Protocol (SOAP) and Web Services Description Language Web services, has become a popular Web application program interface (API) model over the years. A RESTful API, or RESTful Web service, uses both HTTP and REST.
This REST guide brings together a range of stories that highlight when it's best to implement REST, especially in comparison with SOAP and with an API.
REST vs. SOAP
1. When to use REST instead of SOAP
SOA and REST each have favorable qualities and have been compared to each other from the start. Maybe the question shouldn't be whether SOA or REST is best, but rather when they can be combined in order to meet an organization's goals.
REST and APIs
2. Relationship between REST and APIs
Mobile and cloud applications, social networking websites, and automated business processes are among the drivers fueling the need for RESTful APIs. Application architects can find themselves with a good headache if they don't completely understand the technology.
More on REST
3. More on REST uses
Everything from enterprise service buses (ESBs) to health care can have a part in RESTful integration. Here are some other stories involving the platform.