Add a DR overview focused on resiliency with comparison for HA & DR #18490
Conversation
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
kathancox
force-pushed
the
dr-resiliency-comp-overview
branch
from
0e393fb
to
3c7eeca
Compare
Add overview with comparative strategies for DR & HA
kathancox
force-pushed
the
dr-resiliency-comp-overview
branch
from
3c7eeca
to
52ebe0f
Compare
| Resilient deployments aim for continuity in database operation to protect from data loss and down time. To maintain resiliency, it is necessary to build deployments with _high availability_ and _disaster recovery_ coverage. | ||
|
|
||
| - [High availability](#choose-a-high-availability-strategy): Continuous and uninterrupted access to data even in the presence of failures or disruptions to maximize uptime. | ||
| - [Disaster recovery](#choose-a-disaster-recovery-strategy): Recovery from a major incident or disaster to minimize downtime and data loss. |
There was a problem hiding this comment.
Yes, like it. To match the other bullet point, I have changed so they are both verbs.
|
|
||
| As you evaluate CockroachDB's disaster recovery features, consider your organization's requirements for the amount of tolerable data loss and the acceptable length of time to recover. | ||
|
|
||
| - Recovery Point Objective (RPO): The maximum amount of time that an organization can tolerate losing data. |
There was a problem hiding this comment.
"maximum amount of data loss – as measured by time – that an organization can tolerate." Maybe this?
There was a problem hiding this comment.
Added, with parenthesis.
| <table class="comparison-chart"> | ||
| <tr> | ||
| <th></th> | ||
| <th>Single-region replication</th> |
There was a problem hiding this comment.
Is it worth adding "synchronous" replication here?
There was a problem hiding this comment.
Added to both columns here.
| <b>Fault tolerance</b> | ||
| </td> | ||
| <td>Zero RPO node, availability zone failures</td> | ||
| <td>Zero RPO node, availability zone failures</td> |
There was a problem hiding this comment.
The multi-region one should also be able to survive a region failure
| <b>Fault tolerance</b> | ||
| </td> | ||
| <td>Not applicable</td> | ||
| <td>Zero RPO node, availability zone region failure with loss up to RPO</td> |
There was a problem hiding this comment.
nit: i think a comma is needed after 'availability zone'?
There was a problem hiding this comment.
Oh yeah, looks like it! Added the comma!
|
|
||
| As you evaluate CockroachDB's disaster recovery features, consider your organization's requirements for the amount of tolerable data loss and the acceptable length of time to recover. | ||
|
|
||
| - Recovery Point Objective (RPO): The maximum amount of data loss (measured by time) that an organization can tolerate losing data. |
There was a problem hiding this comment.
I think "losing data" should be removed?
| toc: true | ||
| --- | ||
|
|
||
| Resilient deployments aim for continuity in database operation to protect from data loss and down time. To maintain resiliency, it is necessary to build deployments with _high availability_ and _disaster recovery_ coverage. |
There was a problem hiding this comment.
I haven't changed this. Having "database operation" modify "continuity" feels a little harder to read. I have left as-is for now — hopefully my docs review partner may have an idea here.
Fixes DOC-9928, DOC-9929
This PR (in draft) adds a DR overview page to direct users toward establishing resiliency in their deployments. Currently included this as an overview page for DR page, but there are other options.
Rendered preview