Answer: ....
If one load balancer fails, the secondary picks up the failure and becomes active. They have a heartbeat link between them that monitors status. If all load balancers fail (or are accidentally misconfigured), servers down-stream are knocked offline until the problem is resolved, or you manually route around them.
Explanation:
Load balancing is a technique of distributing your requests over a network when your server is maxing out the CPU or disk or database IO rate. The objective of load balancing is optimizing resource use and minimizing response time, thereby avoiding overburden of any one of the resources.
The goal of failover is the ability to continue the work of a particular network component or the whole server, by another, should the first one fail. Failover allows you to perform maintenance of individual servers or nodes, without any interruption of your services.
It is important to note that load balancing and failover systems may not be the same, but they go hand in hand in helping you achieve high availability.
Answer:
It's up to personal preference.
Explanation:
iPhone/Apple gives more compliments to security than Android.
Android has more friendly user GUI and dev tools.
let's say they catch-up to each other after t hour.
so
in t hour distance travelled by Renee
d = speed × time = 50t
in t hour distance travelled by Kim
d = speed × time = 60(t-1) + 0×1 = 60(t-1)
Note: here kim didn't covered any distance in first hour and in rest t-1 hour it travelled all distance
now.as distance travelled by both is same so
60(t-1) = 50t
60t -60 = 50t
adding 60 both sides
60t = 50t+60
subtracting 50t both sides
60t -50t = 50t+60 - 50t
10t = 60
dividing by 10 both sides
t = 60/10 = 6
so in 6 hour both will catch-up to each other
