Jonahx your response summarizes my feelings pretty well. To add to this, I found the post perplexing considering that REST also has cache constraints as describ

Jonahx your response summarizes my feelings pretty well. To add to this, I found the post perplexing considering that REST also has cache constraints as described at http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_4 http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch.... This makes some statements in the article strange. For example: "Very rarely will a RESTful URL specify an Expires header . . ." Leaving aside that Expires is not the only cache header http offers (see http://odino.org/rest-better-http-cache/ http://odino.org/rest-better-http-cache/ for others), the main problem with this statement is that it suddenly makes the system he is describing not-quite-RESTful. It raises the question are you really in a RESTful style if you throw your hands up and ignore the cache part of the style. I would say that ignoring cache is an assumption that Dziuba is making which partly results in the problem he describes, along with having incorrect domain modeling. Restore the cache piece to the system and it would be able to deal with the stale-price-problem just fine by noticing that the price is stale and requesting a fresh one.