> Serializable by default doesn't seem feasible when you really dive into the concept.
I was expecting you'd argue for a weaker isolation level than serializable, but then you said:
> Without any knowledge of the transaction type(s) and their semantics per the business domain, it would be impossible to make assumptions about logical ordering of anything.
Serializable isolation level only guarantees some total order of transactions, and yes, it doesn't guarantee that the order will be exactly what you want (e.g. first come, first serve). So, are you now suggesting strict serializability [1], then?
I was expecting you'd argue for a weaker isolation level than serializable, but then you said:
> Without any knowledge of the transaction type(s) and their semantics per the business domain, it would be impossible to make assumptions about logical ordering of anything.
Serializable isolation level only guarantees some total order of transactions, and yes, it doesn't guarantee that the order will be exactly what you want (e.g. first come, first serve). So, are you now suggesting strict serializability [1], then?
[1] https://jepsen.io/consistency/models/strict-serializable