> author wishes to use the distributed lock service for some purpose that's not well served by distributed locks Exactly. It should be clear that a distributed

> author wishes to use the distributed lock service for some purpose that's not well served by distributed locks Exactly. It should be clear that a distributed lock service has a finite, and low, overall rate of progress. It obviously cannot be in the critical path of every transaction globally. But when using it for events which rarely happen, such as electing a new master of a partition of a database, or some other thing that happens once a week, then the low throughput is not an issue.