REST hurried to the Warehouse Server. In DataVille, everything was a —a noun, not a verb. REST asked for the representation of Product 101 . The Response The Server handed REST a small, clean JSON document:
UserInterface sent a message out across the web highway: GET /products/101 The Journey RESTful Web APIs
Add more technical detail on (POST, PATCH, DELETE) REST hurried to the Warehouse Server
Suddenly, a new client—a mobile app—asked REST for the same item. Because REST was stateless, the server didn't have to manage sessions or cookies, allowing REST to handle thousands of requests seamlessly without getting overwhelmed. The Response The Server handed REST a small,
This was a , a standard HTTP method meant for retrieving data. REST picked up this request. REST didn't care that UserInterface had asked for Product #99 just a second ago. REST didn't know who UserInterface was, and didn't need to know.
Later, UserInterface needed to change the price of the SuperWidget. It sent a new request: PUT /products/101 with the new data.
REST took this, updated the resource, and returned a 204 No Content code—a way of saying "I did it, but I don't need to show you the whole object again". The Departure