Are Mutations Parallel or Synchronous?

[abhimanyusinghgaur]

@verneleem

Is this from the spec or is this dependent on implementation?

It is from spec. All “standard” implementations must adhere to the spec.
And the same happens in Dgraph. Mutations are executed serially in the order they are present in the request.

@verneleem

Do all mutations in an operation run in the same transaction?

No, in Dgraph each mutation runs in a separate transaction, which is committed before the next mutation in the operation is processed. This is what guarantees the behaviour that the spec expects:

This means that if we send two incrementCredits mutations in one request, the first is guarenteed to finish before the second begins, ensuring that we don’t end up with a race condition with ourselves.

@verneleem

Can mutations be separated into their own transactions?

I think, I answered it above. They are already separate.

@verneleem

Does the order of mutations inside an operation effect any of the above?

Answered it at the start itself. Let me clarify it a bit more:
Mutations are executed serially in the order they are present in the request. Where execution of a single mutation consists of these steps in order:

1. Creating a new transaction
2. Running the mutation
3. Committing the transaction

If any error happens in any of the above steps, then the rest of the mutations in the request are not executed.