Confirmed users
927
edits
Services/F1/Server/Architecture: Difference between revisions
Jump to navigation
Jump to search
→Synchronous Architecture
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| Line 35: | Line 35: | ||
3. the server upgrades the status of the service, by incrementing the number of good or bad responses. | 3. the server upgrades the status of the service, by incrementing the number of good or bad responses. | ||
== Load Balancing == | |||
A simple way to balance the load is to have servers dedicated to a specific service. | |||
A X-Target-Service header set by the server can define which service is going to be called and a Zeus load balancer can dispatch the request to a specific subset of servers. This will allow a fine-tuning of the pooling capacity of the web server and also will let us specifically add more servers per service. | |||
= Asynchronous Architecture = | = Asynchronous Architecture = | ||