| title | summary | toc |
|---|---|---|
When to use REGIONAL vs. GLOBAL tables |
Learn how to use CockroachDB's improved multi-region user experience. |
false |
New in v21.1: Table Localities tell CockroachDB how to optimize access to a table's data in a multi-region cluster. CockroachDB uses the table locality setting to determine how to optimize access to the table's data from that locality.
The following table localities are available:
REGIONALGLOBAL
Use REGIONAL tables if:
- Your application requires low-latency reads and writes from a single region (either at the row level or the table level).
- Access to the table's data can be slower (higher latency) from other regions.
Use GLOBAL tables if:
- Your application has a "read-mostly" table of reference data that is rarely updated, and that needs to be available to all regions.
- You can accept that writes to the table will incur higher latencies from any given region, since writes use a novel non-blocking transaction protocol that uses a timestamp "in the future".
For more information about how to choose an overall multi-region configuration, see Choosing a multi-region configuration.
{{site.data.alerts.callout_success}} {% include {{page.version.version}}/misc/multiregion-max-offset.md %} {{site.data.alerts.end}}
{% include enterprise-feature.md %}