+For creating, updating and deleting data, I prefer to retain the conventional REST approach. In my view, it’s simply more practical. Handling the creation of multiple objects in a single request, as GraphQL allows, can quickly become problematic. If part of the request fails, it forces tough decisions: should everything fail or only the problematic items? Partial failures can frustrate users and often require implementing rollback endpoints to let users undo operations if they change their minds. What about side effects of the action to rollback? Keeping mutations in REST keeps this logic clear, predictable and easier to manage from the backend perspective.
0 commit comments