1.
I think though you&#x27;d really want to have some measurements regarding the performance impact of things like over fetching.<p>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&#x2F;2 you get extra efficiency advantages (e.g. lots of more granular resources can be retrieved over a single connection).<p>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.<p>3.
Not sure that&#x27;s an argument against going resource oriented, if you don&#x27;t find the debate interesting just ignore it.