POST breaks http caching and is non-idempotent. This is terrible advice for any API that cares about scaling and performance. You will for sure paint yourself into a corner and then adopt a completely different tech because you made such a mess of the "REST" way you will conclude it has bad performance. Check out etags which you will be locked out of. You will not get the free performance benifits of browser etag support