Good paper. transaction log\WAL storage for OLTP databases doesn't belong in S3 (for datalakes... maybe?).
The design proposed in the paper is very similar to the HorizonDB WAL server.
There is a lot of hype around putting the WAL on object storage.
However, for low-latency systems, e.g. OLTP databases, object storage is a suboptimal primitive for the WAL:
(1) PUTs are expensive for small WAL writes [bytes/$].
(2) Object stores are optimized for throughput,
