As an engineer or developer, it's important to keep up with the latest programming innovations. As with many other API developers, I've opted for a tried-and-true, simplified approach to our data validation APIs that is REST.
The REST architecture generally consists of clients, servers, resources, and a vocabulary of HTTP operations known as request methods. In essence, clients send requests to servers and servers respond. These interactions are centered around representations of resources such as a document or URI. These representations are typically exchanged over a standardized interface such as HTTP. Clients, servers, and other connectors can mediate requests without having to know anything beyond the resource's identifier, required action, and the format of the representation that must be returned such as JSON or XML.
REST uses a standardized set of request methods including: GET, POST, PUT, DELETE, and other existing HTTP capabilities.
EXAMPLE OF REST API
BENEFITS OF REST API
- REST is much easier than other approaches such as SOAP which keeps developers from having to reinvent the wheel as far as HTTP request operations go. SOAP also requires separate server and client programs.
- REST is based on standard HTTP operations, and it uses verbs with specific meanings such as "get" or "delete" for clarity. Resources are assigned individual URIs, adding flexibility.
- With REST, information that is produced and consumed is separated from the technologies that facilitate production and consumption. As a result, REST performs well, is highly scalable, simple, and easy to modify and extend.
WHY I LOVE IT
The thought of writing one back-end code for all your platform applications with easy accessibility, not reinventing the wheel, scalability, extend and modify is a joy for me.
Lets connect @ Twitter
Download this rest api tutorial for a start @ REST API - Github
Top comments (0)