Run Postgres replicas next to your users

A read that crosses an ocean costs 80 ms before the database does any work. A replica in the same city costs about 2.

Lattice keeps one primary per database and adds read replicas in the regions your traffic comes from. Reads go to the nearest copy; writes go to the primary and reach every replica within a second.

Turn it on with one line in lattice.toml, or let the platform add replicas where reads pile up. This guide walks through both, and how to pin a table to one region when the law says so.