[crunchyyoda]

> the simplest avoidance algorithm being simply to always acquire locks in the same order.

Sounds simple, but I remember being in the weeds once or twice with a custom application deadlocking (and not enjoying it much).

With ORMs, I guess they can take the reins in terms of which resources they update and in what order, but I'm curious what other people do in the absence of that? Manually worrying about the order of which tables get updated in all of your service calls seems like it'd get hard the larger the app becomes or the more developers involved.