Idempotency is an important attribute for correctness. Yep, you can document that POSTing to $ENDPOINT is idempotent, but you can't communicate that to caching layers throughout the network. QUERY, by definition, is idempotent and cacheable.
replyGreat point. I wish more people realized that intuitively.
replyDoes anyone know if this approach works at significantly larger scales? Curious about where it breaks down.
replyLarger scales like what? I expect that everywhere you currently cache GETs you can cache QUERYs. But does caching GETs work at scale?
replyAt least support - or lack thereof - for a new verb is unambiguous (compared to changing the semantics of GET)
reply