“Serializability: multi-operation, multi-object”, but why?

Explores why serializability in databases is specifically relevant to multi-operation, multi-object transactions. Traces the concept through authoritative sources like Martin Kleppmann's "Designing Data-Intensive Applications" and Peter Bailis's work. Demonstrates that while serializability technically applies to single-operation transactions, it becomes trivial in those cases since weaker isolation levels like read committed already provide equivalent guarantees. The distinction matters because weak isolation levels only diverge from serializability when transactions involve multiple operations or objects, where one operation can execute before another transaction commits while a second operation executes after.