How does Databricks Lakebase/neon mask network latency during synchronous WAL flushes while keeping ACID guarantees?

Since Lakebase uses a decoupled storage and compute architecture, the synchronous WAL flushes have to travel over the network to the distributed storage layer. How is Databricks Lakebase avoiding the standard network round-trip penalty per transaction commit? submitted by /u/Alternative-Fig-6465 [link] [留言]