Confirmed users
927
edits
Services/F1/Server/ServicesStatusDB: Difference between revisions
Services/F1/Server/ServicesStatusDB (view source)
Revision as of 13:19, 29 April 2011
, 29 April 2011→Principle
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| Line 8: | Line 8: | ||
1. On every request the client adds a X-Target-Service header containing the domain of the service it wants to reach. | 1. On every request the client adds a X-Target-Service header containing the domain of the service it wants to reach. | ||
For example, if the clients want to share on Twitter, a "X-Target-Service: twitter.com" is added. | |||
2. The web server (NGinx) that receives the query ask the Services DB what is the status of the service (as described later) and decide if the query should go through or not. | 2. The web server (NGinx) that receives the query ask the Services DB what is the status of the service (as described later) and decide if the query should go through or not. | ||
| Line 18: | Line 18: | ||
5. If the upstream server succeeds, it notifies asynchronously the Services DB | 5. If the upstream server succeeds, it notifies asynchronously the Services DB | ||
6. If the upstream server fails. e.g. if the third party service is considered down, it notifies | 6. If the upstream server fails. e.g. if the third party service is considered down, it notifies asynchronously the Services DB | ||
= Client UX on outage = | = Client UX on outage = | ||