RESTful API by abubakar

RESTful API by abubakar

• 1.
  RESTful Web services:The basics Presented by: Abubakar
• 2.
  RESTful Web services:The basics Representational State Transfer (REST) has gained widespread acceptance across the Web as a simpler alternative to SOAP- and Web Services Description Language (WSDL)-based Web services. SOAP, originally defined as Simple Object Access protocol, is a protocol specification for exchanging structured information in the implementation of web services in computer networks. The Web Services Description Language (WSDL pronounced "wiz'-dul") is an XML-based interface definition language that is used for describing the functionality offered by a web service.
• 3.
  Key evidence ofthis shift in interface design ● Yahoo ● Google ● Facebook
• 4.
  The basic ●REST defines a set of architectural principles by which you can design Web services that focus on a system's resources, including how resource states are addressed and transferred over HTTP by a wide range of clients written in different languages.
• 5.
  History ● RESTdidn't attract this much attention when it was first introduced in 2000 by Roy Fielding at the University of California, Irvine, in his academic dissertation, "Architectural Styles and the Design of Network-based Software Architectures," which analyzes a set of software architecture principles that use the Web as a platform for distributed computing (see Resources for a link to this dissertation).
• 6.
  ● REST asksdevelopers to use HTTP methods explicitly and in a way that's consistent with the protocol definition. This basic REST design principle establishes a one-to-one mapping between create, read, update, and delete (CRUD) operations and HTTP methods. According to this mapping: ● To create a resource on the server, use POST. ● To retrieve a resource, use GET. ● To change the state of a resource or to update it, use PUT. ● To remove or delete a resource, use DELETE.
• 7.
  Common MIME typesused by RESTful services MIME-Type Content-Type JSON application/json XML application/xml XHTML application/xhtml+xml Note: MIME: Multipurpose Internet Mail Extensions
• 8.
  Conclusion ● RESTis not always the right choice. It has caught on as a way to design Web services with less dependence on proprietary middleware. ● As you've examined in the so-called principles of RESTful interface design, XML over HTTP is a powerful interface that allows internal applications, such as Asynchronous JavaScript + XML (Ajax)-based custom user interfaces, to easily connect, address, and consume resources. ● In fact, the great fit between Ajax and REST has increased the amount of attention REST is getting these days. ● Exposing a system's resources through a RESTful API is a flexible way to provide different kinds of applications with data formatted in a standard way.
• 9.
  Thank YOU !!!