title: Is it good practice to bundle multiple GQL mutations to one HTTP call
body: <p>I have a mutation on my GQL server. The resolver for this basically just proxies the request to a backend Java service that handles Dynamo table mapping. I cant really edit anything on that service right now. </p>
  
  <p>The mutation signature looks like this: </p>
  
  <pre><code>mutation {
    addItemRelation(child:"child1Id", parent:"parentId"),
  }
  
  mutation {
    removeItemRelation(child:"child1Id", parent:"parentId"),
  }
  </code></pre>
  
  <p>On the front end I have an interface that lets me check boxes to relate certain properties to the parent item. Currently the way I handle this is by calculating the items to add/remove. Then sending one HTTP call to GQL per item. </p>
  
  <p>Im wondering would it be better to bundle these all into one request. For example, if I was adding 2 items and removing one I could compute a GQL query like this. </p>
  
  <pre><code>mutation {
    addItemRelation(child:"child1Id", parent:"parentId"),
    addItemRelation(child:"child2Id", parent:"parentId"),
    removeItemRelation(child: "child3id", parent: "parentId")
  }
  </code></pre>
  
  <p>Would this be considered better practice than sending out 3 separate http requests? </p>