Merge pull request #175560 from fsautomata/patch-1

HA - removed RTO <15mins

Author: PRMerger4

articles/cosmos-db/consistency-levels.md

@@ -164,18 +164,18 @@ The exact RTT latency is a function of speed-of-light distance and the Azure net
 
 ## <a id="rto"></a>Consistency levels and data durability
 
-Within a globally distributed database environment there is a direct relationship between the consistency level and data durability in the presence of a region-wide outage. As you develop your business continuity plan, you need to understand the maximum acceptable time before the application fully recovers after a disruptive event. The time required for an application to fully recover is known as **recovery time objective** (**RTO**). You also need to understand the maximum period of recent data updates the application can tolerate losing when recovering after a disruptive event. The time period of updates that you might afford to lose is known as **recovery point objective** (**RPO**).
-
-The table below defines the relationship between consistency model and data durability in the presence of a region wide outage. It is important to note that in a distributed system, even with strong consistency, it is impossible to have a distributed database with an RPO and RTO of zero due to [CAP Theorem](https://en.wikipedia.org/wiki/CAP_theorem).
-
-|**Region(s)**|**Replication mode**|**Consistency level**|**RPO**|**RTO**|
-|---------|---------|---------|---------|---------|
-|1|Single or Multiple write regions|Any Consistency Level|< 240 Minutes|<1 Week|
-|>1|Single write region|Session, Consistent Prefix, Eventual|< 15 minutes|< 15 minutes|
-|>1|Single write region|Bounded Staleness|*K* & *T*|< 15 minutes|
-|>1|Single write region|Strong|0|< 15 minutes|
-|>1|Multiple write regions|Session, Consistent Prefix, Eventual|< 15 minutes|0|
-|>1|Multiple write regions|Bounded Staleness|*K* & *T*|0|
+Within a globally distributed database environment there is a direct relationship between the consistency level and data durability in the presence of a region-wide outage. As you develop your business continuity plan, you need to understand the maximum period of recent data updates the application can tolerate losing when recovering after a disruptive event. The time period of updates that you might afford to lose is known as **recovery point objective** (**RPO**).
+
+The table below defines the relationship between consistency model and data durability in the presence of a region wide outage.
+
+|**Region(s)**|**Replication mode**|**Consistency level**|**RPO**|
+|---------|---------|---------|---------|
+|1|Single or Multiple write regions|Any Consistency Level|< 240 Minutes|
+|>1|Single write region|Session, Consistent Prefix, Eventual|< 15 minutes|
+|>1|Single write region|Bounded Staleness|*K* & *T*|
+|>1|Single write region|Strong|0|
+|>1|Multiple write regions|Session, Consistent Prefix, Eventual|< 15 minutes|
+|>1|Multiple write regions|Bounded Staleness|*K* & *T*|
 
 *K* = The number of *"K"* versions (i.e., updates) of an item.