Resource Routes - PUT vs PATCH

Assuming that PATCH makes it possible to update one attribute at a time

Wrong assumption. You can update as many attributes as you want.

No. Yes, with PATCH you can update as many attributes as you need individually. But, as I understand it, the PUT is used to replace the entire entity.

I believe that PATCH makes the application more flexible because it does not "force" the client to send all the attributes to be updated, but only what is necessary.

I saw in most of the documentation recommending the use of PUT as the default for updating, but studying the difference between PUT and PATCH I had this doubt.

Here are some opinions and examples to take into consideration: https://stackoverflow.com/questions/2845...e-examples

 natanfelles.github.io