How to choose between SOAP and REST Web services
SOAP and REST offer different methods to invoke a web service. Learn the variations between the two approaches, including integration concerns and client choices. Read Now
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.
1Relationship 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.
REST approach gains popularity with software pros
Software developers are demanding APIs that are delivered in a RESTful, resource based way, and one way to do that is by building with the RESTlet framework. Read Now
Naming strategies for RESTful Web services
New descriptive languages like WADL and WSDL 2.0 are making it possible to describe the RESTful contract to client applications. However, if your RESTful web services are not named effectively, the mechanism for describing the interface may run out of steam. Read Now