The Netflix client/SDK was configured to contact 3 different regions. I'm guessing somehow, on the backend, it was replicating the state of your request to the other three regions. If one regions were to fail, the client would query the other two regions and regain its state.
Having 3 regions available - the other two should be able to pick up the load of losing one without hitting capacity.
The Netflix client/SDK was configured to contact 3 different regions. I'm guessing somehow, on the backend, it was replicating the state of your request to the other three regions. If one regions were to fail, the client would query the other two regions and regain its state.
Having 3 regions available - the other two should be able to pick up the load of losing one without hitting capacity.