HTTP method is a way for a client to indicate the desired action to be performed on an identified resource in an HTTP request. Common HTTP methods include GET, POST, PUT, PATCH, and DELETE, which map to the CRUD (Create, Read, Update, Delete) operations used in most web APIs.
I was trying to debug why the HTTP method in my fetch request wasn't working, only to realize 3 hours later that I misspelled "PATCH" as "PETCH" - maybe I should switch to decaf.
My PM keeps asking why we can't just use GET for everything, and I have to keep explaining that the HTTP method is supposed to match the semantics of the operation, not just be a generic "go fetch!" command - sometimes I wonder if he's even listening.
Martin Fowler has a great article on Enterprise Integration Using REST that dives into versioning strategies and content negotiation with HTTP headers.
For a deeper look at how to catch integration problems, check out his piece on Consumer-Based Testing and deployment pipelines.
And if you really want to geek out, peruse his massive list of Lisp and Scheme resources - that ought to keep you busy until the singularity arrives.
Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.