Use an airline-controlled "snapshot isolated" database to maximise this example. This maximises this example. What if the airline's better performance was due to a non-serialized execution?

If you want to get the most out of this example, you should definitely begin by using a database that is "snapshot isolated" and is controlled by an airline. This will allow you to get the most out of this example. What if, rather than an operation that can be serialized, the improved overall performance of the airline was due to an execution that cannot be serialized?

Consider the term "snapshot isolation" as an example for a database used by an airline. Is the selection of a strategy that does not lend itself to serialization suitable in the event that airlines are able to improve their overall performance?

As an example, consider "snapshot isolation" in the context of a database for an airline. If airlines can improve their overall performance, is a non-serializable strategy acceptable?