Hacker News Reader

For PlanetScale Metal, we use semi-sync replication. The primary need to get an ack from at least one replica before committing.

Soo... We have a network hop after all?

For writes, yes. But what if your workload is 90% reads?

It makes a lot of sense for read-heavy workloads, for sure!

I was just trying to get a better understanding of what is happening under the hood :)

Is that ack sent once the request is received or once it is stored on the remote disk?