All geek questions in one place

REST without PUT

The ThoughtWorks Technology Radiator July 2014 mentions in the Technique / Trial section a new trend called REST without PUT . They explain this as follows:

In the last radar, we talked about capturing the Explicit Domain Event, focusing on recording business-significant events that caused transitions, not just CRUDing objects. REST interfaces typically use PUT to update the status of a resource, however it is often better to POST to record a new resource event that captures the intent. REST without PUT has the lateral advantage of separating command and request interfaces and forcing consumers to allow for possible consistency.

Are there any additional resources where you can read about this? Is the term REST without PUT idea written by ThoughtWorks, or is it something academic or ...?

Any hints of this?

+6
source share
2 answers

IMHO they say that you should stop looking at CRUD operations and focus on state transitions. Then you map many transitions to specific events. One of them is used to update the object. How it will be updated and what will be updated, the context of the event is determined. It is necessary to update the POST event instead of updating the PUT.

BTW, which solves one problem using pure HTML in REST - HTML does not allow PUT or DELETE to run without JavaScript.

+3
source

REST without PUT is not standard; you guessed it, this is just a ThoughtWorks thing.

+1
source

Source: https://habr.com/ru/post/977396/

More articles:


All Articles