REST Services Overview

REST stands for Representational State Transfer. It relies on a stateless, client-server, cache-able communications protocol and in virtually all cases, the HTTP protocol is used.

REST is an architecture style for designing networked applications. Rather than using complex mechanisms such as SOAP to connect between machines, simple HTTP is used to make calls between machines.

REST applications use HTTP requests to post data (create and update), read data (for example make queries), and delete data. Thus, REST uses HTTP for all four CRUD (Create, Read, Update or Delete) operations. REST is a lightweight alternative to mechanisms like RPC (Remote Procedure Calls) and Web Services (SOAP, WSDL, etc). Despite being simple, REST is fully-featured and there is basically nothing you can do in Web Services that cannot be done with a REST architecture.

• REST Service Methods
  The various methods of REST services are as follows:
• REST Service Endpoint
  This default URL format for the endpoint is:
• REST Service Resource
  In any REST service it is good to have all the resources structured by their hierarchy. The resources are then specified in the hierarchical part of the URL. The hierarchical parts are required and unique.
• REST Service Header
  REST call headers are in fact HTTP headers, a required component of the message. They denote the operating parameters of the transaction, also called as metadata.
• REST Service Parameters
  
• REST Service Request Body
  

Copyright © Cloud Software Group, Inc. All rights reserved.