# Overview An approach to [[Strong (or Serializable) Isolation]] where transactions are literally completed one-at-a-time (i.e., serially). # Key Considerations # Pros # Cons # Use Cases - Every transaction must be small and fast, because it takes only one slow transaction to stall all transaction processing. - It is limited to use cases where the active dataset can fit in memory. Rarely accessed data could potentially be moved to disk, but if it needed to be accessed in a single-threaded transaction, the system would get very slow. - Write throughput must be low enough to be handled on a single CPU core, or else transactions need to be partitioned without requiring cross-partition coordination. - Cross-partition transactions are possible, but there is a hard limit to the extent to which they can be used. # Related Topics - [[Redis]] - [[Datomic]] - [[VoltDB]]