RESTful API Overview

RESTful API Parsing

1, what is the restful API.

Rrst:representational State Transfer (representational status handover or representational state transfer)

Rrst a software architecture style that defines a set of architectural principles that programmers use to design resource-centric Web services (APIs)

Maximum characteristics: simple.

REST is often built on widely popular protocols and standards such as http,uri,xml,html.

Amazon, Yahoo and so on.

Client <==>server

Page state transitions

Status: An open page, a URL address content (still).

Conversion: page or content changes.

Stateless: Server does not rely on client state.

Both server and client have status.

As long as there is a state of things that are still.

Stateless: Do not rely on each other's state.

Web Apps

HTTP

Url

2, RESTful API pros and cons.

Relying on protocols or standards such as HTTP, reuse conventions, easy integration.

Build services that change from times to times.

Eliminates client throttling for the API.

It contains all the parameters, contexts, and data required to generate a response from a server-side component in the header and body.

Because of its characteristics:

Enables load balancing, failover, proxy, and gateway server clusters to be organized in a service topology, allowing requests to be routed from one server to another as needed, reducing overall response time for Web service calls.

To scale up with an intermediary server, the REST application needs to send a separate, complete request, and the server processes the request without relying on the application context or state.

Cons: Rely on HTTP and other protocols, have some relevant technical understanding, in order to correctly build the rest format API.

RESTful API Overview