Skip to content

Commit

Permalink
Merge pull request #10968 from cockroachdb/20210726-choosing-multireg…
Browse files Browse the repository at this point in the history
…ion-configs

Fix errors on 'Choosing a multiregion config' page
  • Loading branch information
rmloveland authored Jul 27, 2021
2 parents 42fb926 + f048a35 commit 3bbcedf
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion v21.1/choosing-a-multi-region-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ The table below offers another view of how the configuration options described a
|---------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `REGIONAL BY TABLE` | Low-latency for single-region writes and multi-region stale reads. | Single-region writes are higher latency than for ZONE, as at least one additional region must be consulted for each write. Stale multi-region reads are of comparable latency to ZONE survival. |
| | For single-region apps that can accept risk of region failure. | For single-region apps that must survive region failure. |
| `REGIONAL BY ROW` | Low-latency consistent multi-region reads & writes for rows which are homed in specific regions. | Low-latency consistent multi-region reads. Low-latency single-region writes if you are writing to a row from its home region. |
| `REGIONAL BY ROW` | Low-latency consistent multi-region reads & writes for rows which are homed in specific regions. | Low-latency consistent reads from a row's home region. Low-latency consistent [stale reads](follower-reads.html) from outside the row's home region. Low-latency writes if you are writing to a row from its home region. |
| | For multi-region apps which read/write individual rows of the table from a specific region, and can accept the risk of region failure. | Same as for ZONE survival, but for apps that must survive a region failure. |
| `GLOBAL` | Low-latency multi-region reads. Writes are higher latency than reads. | Low-latency multi-region reads. Writes are higher latency than reads. There should be minimal difference in write latencies between ZONE and REGION survival due to a new custom non-blocking transaction protocol. |
| | For multi-region apps that need low-latency reads of a "read-mostly" table. | For multi-region apps that need low-latency reads of a "read-mostly" table, and the ability to survive region failures. |
Expand Down

0 comments on commit 3bbcedf

Please sign in to comment.