I agree that those cases would be tough to make work in a &quot;clean&quot; or at least standard RESTful API design but it&#x27;s really improbable to encounter them.<p>1. This issue could be attributed to the database schema design imo.<p>2. In what case would you want to delete multiple comments at the same time ? I&#x27;m not trying to argue for the sake of arguing but I&#x27;ve genuinely never had to remove parts of an array that were not either a single element or the whole array.<p>3. Again I don&#x27;t see a scenario where you would have to do this. If it&#x27;s a consequence of another API call for example: You DELETEd a &quot;group&quot; so all of its member &quot;users&quot; should be deleted too. Than this kind of side effects or consistency CRUD should be handled inside the DELETE API call of the &quot;group&quot;.<p>I don&#x27;t think that REST API design pretends to answer every single business logic use case but it does answer most of the common ones.<p>In my opinion it&#x27;s also dangerous to use a library that will abstract those difficult &#x2F; unconventional use cases because they will feel easy to solve and hide the inherent complexity and cost that is present in the Database queries.