Confirmed users
927
edits
Services/F1/Server/Architecture: Difference between revisions
no edit summary
Tarek.ziade (talk | contribs) No edit summary |
Tarek.ziade (talk | contribs) No edit summary |
||
| Line 20: | Line 20: | ||
The average size of data a user transfers through our servers is 16 bytes per day. So if a queue stores this data, it represents 1.5 Gbyte / day for 100M users. | The average size of data a user transfers through our servers is 16 bytes per day. So if a queue stores this data, it represents 1.5 Gbyte / day for 100M users. | ||
= Synchronous vs Asynchronous = | |||
Synchronous: | |||
* ++ fast to set up (uses the existing app) | |||
* + can evolve to an async version later (by adding a GET /result) | |||
* - need to keep connections open | |||
* -- any service failure ends up with a 503 to the client | |||
Asynchronous: | |||
* ++ short services down times are transparent to the client | |||
* + no need to keep connections opened | |||
* (+) (potentially) allow smart requests (batches) over services | |||
* - more traffic (polling) | |||
* - more pieces in the chain : more work to tweak/stabilize the architecture. | |||
* -- longer to do - requires much more coding, more tweaking | |||
= Synchronous Architecture = | = Synchronous Architecture = | ||