
RESTful Web services may be simpler, more versatile, and more scalable than other Web services, but the REST architecture still requires explanation. Readers get more than 50 recipes to help them solve problems they're likely to face when developing RESTful Web services.
Also remember that having a resource oriented design and working well with HTTP gives you out of the box advantages in terms of caching and validation, and in HTTP/2 you get extra efficiency advantages (e.g. lots of more granular resources can be retrieved over a single connection).
2. There are patterns for that though, often best approach is to represent that transaction as a resource. Restful Web Services Cookbook covers approaches for these sorts of bulk operations.
3. Not sure that's an argument against going resource oriented, if you don't find the debate interesting just ignore it.
It's nice to see a CC-licensed effort to create a similar resource. It's unfortunate that the names are so similar.
Here are two of my favorite REST resources (pun intended).
Richardson Maturity Model: steps toward the glory of REST
http://martinfowler.com/articles/richardsonMaturityModel.htm...
RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity
http://www.amazon.com/gp/product/0596801688
And I am looking forward to widespread adoption of the REST problem standard posted here a few weeks ago.
http://www.ietf.org/id/draft-ietf-appsawg-http-problem-00.tx...
It's amazing, really. It's not just a recipies list, it explains a lot of very important REST cases, and also when to use or not to use REST.