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.

▲

resters 2 hours ago | parent | next [-]

Great point. I wish more people realized that intuitively.

▲

jnewton_dev 5 hours ago | parent | prev [-]

Does anyone know if this approach works at significantly larger scales? Curious about where it breaks down.

	▲	inigyou 4 hours ago \| parent [-]
		Larger scales like what? I expect that everywhere you currently cache GETs you can cache QUERYs. But does caching GETs work at scale?