Deterministic ordering means that a service is guaranteed to receive messages from a single requestor in the same order that the requestor sent them. Obviously, this can make designing the service much easier than non-deterministic ordering, especially if the requestor and the service must engage in a multi-step conversation. However, deterministic ordering can require more computational and network resources, so it shouldn’t be used if it’s not needed.