The good thing about REST is that the limited vocabulary enforces good design practices, but it doesn't save you from fundamental problems. On the article, tha

The good thing about REST is that the limited vocabulary enforces good design practices, but it doesn't save you from fundamental problems. On the article, that would be the conceptual mistake of considering the price is an attribute of the product, which in turn would require a second request to retrieve, then breaking the atomicity of having all the necessary state in a single request. To solve that, he proposed a "database over REST", where the main resources act like an index - thus increasing the abstraction by one notch and moving some complexity to the client. This doesn't solve a problem inherent to REST, but rather a conceptual problem that applies to all data systems, which is how to maintain and recall states in an atomic way.