Figure 7-11 is a sequence diagram for the example we’ve
been looking at, where a user wants to get list of all
rooms in the house. For this example, assume that there
is a web application with a user interface that renders the
list of all the rooms and the various attributes of the
rooms.
Figure 7-11 Sequence Diagram Showing End-to-End
Flow
The sequence of events that occur is as follows:
1. The client browser points to http://myhouse.cisco.com/ (the
HTTP GET request sent), which is the web application.
2. The server sends out a REST API request to get all the rooms to
the back-end service (/API/getallrooms) to get all the details of the
house.
3. The back-end API service returns data in JSON format.
4. The web application processes the JSON and renders the data in
the user interface.
5. The client sees the data.REST CONSTRAINTS
REST defines six architectural constraints that make any
web service a truly RESTful API. These are constraints
also known as Fielding’s constraints (see