You may use the phrase "snapshot isolation" as an illustration of how a database for an airline could be created in the future. If airlines are able to improve their performance across the board, then maybe it would be okay for them to use a system that cannot be serialized.

A good example of a database that benefits from snapshot isolation is an airline's reservation system. The airline could be willing to accept non serializable execution if it means greater overall performance.

For example, consider a database for an airline that uses snapshot isolation. To achieve greater overall performance, the airline may be willing to accept nonserializable execution.

Consider a database used by an airline, where "snapshot isolation" is used. It's possible that airlines might be willing to accept a non-serializable solution if it meant better overall performance.

To illustrate how "snapshot isolation" may be used in the context of creating an airline database, consider the following scenario. If airlines can improve their overall performance, then maybe a non-serializable system might be acceptable.

Although you always wanted to be a dog trainer, you ended up being an expert on databases because you love to work with data and logic. Your old love is still there, however, so you set up a database company, DogTraining, that builds a product for dog kennels. The core of this product is a database with a schema that captures all the information that kennels need to maintain. Kennels keep information about dog trainers, the First and Last names of the dog trainers (which are unique), birthplace, color of the dog trainers hair, and style of training.  For each dog, the trainer, the date the dog was born, a name (not unique), the type of dog (e.g., Brittany, German Shepard, Collie, etc.), color of the dog’s hair, and how much weighs must be stored. Dogs are also classified into groups of various kinds, for example, hunting, guard, working; a given dog may belong to more than one group. Each group is identified by a name (like those just given) that describes the group. Finally, kennels…

This example might be improved by starting with a database maintained by an airline that employs "snapshot isolation." What if, rather of increasing the airline's overall performance, a non-serializable execution did so?

A database used by an airline that implements "snapshot isolation" serves as an excellent starting point for this example. What if a non-serializable execution results in a better overall performance for the airline?

Let's look at an airline database to see how snapshot isolation is used in practice. The airline, for instance, could agree to a nonserializable execution if it means better long-term outcomes.

Take the case of a snapshot-isolated database used by an airline. I was wondering if you could provide me an example of a non-serializable execution that the airline would be prepared to tolerate in exchange for improved performance.