What is the difference between a PUT and a PATCH request?

[@jgoebel]

What do you think about this video? Let me know in the comments below

[@paulwong7224]

Great video. Thanks! My summary: PUT - Creates or replaces entirely PATCH - Updates fields

[@jgoebel]

yes, that about sums it up 👍

[@yohananmiteo6574]

This is the explanation I was looking for since a long time… Thanks a lot

[@jgoebel]

Glad to hear that

[@abhiramsatpute]

Amazing! My understanding from this video is that PUT is analogous to object-like storage in S3, and also it comes with high security risk of data manipulation

[@MnAino]

I've been following up some tutorials from your Chanel, and OMG! The best practices and concise information are amazing! Hope you are doing well, kind of miss you already.

[@jgoebel]

Glad you like them!

[@DikshaTVblogs]

Great explanation! Thank you…

[@rijuroy7415]

Very clearly described the difference. Thanks a ton.

[@jgoebel]

Glad it helped

[@georgesmith9178]

Yes, I noticed times and again that whoever wrote the specification did not really go over them logically and make sure there was no overlap. The explanation here was good. The reality though is staggering as developers who never read the spec "REST-ful", or should I say REST-like code. Of course, I can't blame them - they are constantly assigned 2.5 their possible workload ALL the time. So who has time to read the spec!? The managers just wants them to close the tickets, so the report looks good.

[@jgoebel]

True, but I found that if you know the theory and the spec, you can get things done way faster and have less stress in the long run

[@simonIsDev]

It's so very useful for me, thanks you very much

[@jgoebel]

Glad it helped!

[@louiskwan4970]

What if there are nested objects or arrays ? Or the entities are always 1 level ?

[@joshuabolanoshernandez4911]

Very clear. Tysm!

[@jgoebel]

Glad it was helpful!

[@hetalchavan7379]

I am a tad bit confused about following statements: 1. Put can be used to create a resource which doesn't exist 2. While trying to replace a resource which doesn't exist, an error will be thrown. Can you please clarify the above?

[@jgoebel]

1. PUT overrides whatever resource is specified under the URL with the payload you send. If the resource does not exist, then it will create it. That is how it is specified in the HTTP RFC 2. Patch updates individual fields of a resource, i.e. if the resource does not exist, then there will be an error

[@yusiff]

Thanks!

[@jgoebel]

👍

[@WhiteSiroi]

nice, thank you very much

[@jgoebel]

Welcome 😊

[@astartesidon609]

dats why i always use patch when updating

[@NoName-oh9fh]

Куда ты пропал?