Confirmed users
927
edits
Services/F1/Server/ServicesStatusDB: Difference between revisions
Services/F1/Server/ServicesStatusDB (view source)
Revision as of 13:25, 29 April 2011
, 29 April 2011→Goal
Tarek.ziade (talk | contribs) (→Goal) |
Tarek.ziade (talk | contribs) (→Goal) |
||
| Line 1: | Line 1: | ||
= Goal = | = Goal = | ||
When a third party service like Twitter gets down or is starting to be very slow, clients will retry to send to our server more and more requests and our infrastructure will be overloaded and potentially unresponsive. | When a third party service like Twitter gets down or is starting to be very slow, clients will retry to send to our server more and more requests and our infrastructure will be overloaded and potentially unresponsive. See the rational section. | ||
The goal of the Services Status DB is to provide to every web server in our infrastructure a status of every third party service. The web server can decide to preemptively back off any new request to that | The goal of the Services Status DB is to provide to every front web server in our infrastructure a status of every third party service in usage. The web server can decide to preemptively back off any new request to the services that are down in order to avoid piling up unnecessary work. | ||
= Principle = | = Principle = | ||