I'm curious about how people use PUT and PATCH in RESTful APIs. From what I understand, PUT is typically meant for replacing an entire resource, while PATCH is used for smaller updates, such as changing just a single field or toggling a status. It feels like that's how most of us operate, but I've also heard some differing views. Are there any other common practices or perspectives on this that I might be missing?
5 Answers
You’ve got the standard thinking down! Just remember that technically, PUT replaces an entire resource while PATCH modifies specific attributes. Ideally, PATCH uses a JSON patch document to be strict about the changes, but most teams go with what works for them. Are you applying this knowledge in a real project?
It's really about intent rather than size. PUT replaces the entire resource, while PATCH is for partial updates. So if you're thinking about it that way, you're spot on! But honestly, a lot of people mix them up in practice. Like, I've seen instances where a PUT should probably be a PATCH, just because of how folks use it.
And then there's POST thrown in the mix just to confuse everyone even more! It's a mess.
In my case, I'm mostly using GraphQL, where everything is treated as a POST request—even queries. It’s interesting how that shapes the way I think about updates! Maybe I'll name my GraphQL server Post Malone just for fun.
You’re on the right track! Most people think of PUT as a full update and PATCH as a way to make smaller changes. In reality, though, many APIs barely utilize PATCH at all; I’ve mostly come across GET and POST myself.
Exactly! It’s rare to find a true PUT function in practice since most fields aren't even editable once they’re set.
Honestly, I avoid PATCH unless it's necessary. I prefer to use POST for most of my backend operations, sending events to indicate that something happened rather than just updating state. It keeps things flexible but sometimes leads to tight coupling with the internal data structure.
I get you! The standard REST approach often fails in complex scenarios where processes can't be simply described with CRUD operations.
Totally agree! It seems like REST's limitations only show up more when you’re building complicated systems.
Right? It's kinda funny how many places misuse the verbs. But I guess no one really cares about the technicalities too much these days!