Confirmed users
1,022
edits
CloudServices/Roadmaps/Campaign-Manager: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Roadmaps/Campaign-Manager (view source)
Revision as of 23:16, 4 October 2012
, 4 October 2012→Sample call
| Line 124: | Line 124: | ||
Note: Firefox will handle this automatically, displaying the chosen URL (i.e. http://mozilla.org/get-your-awesome-on ) | Note: Firefox will handle this automatically, displaying the chosen URL (i.e. http://mozilla.org/get-your-awesome-on ) | ||
TODO: which redirect code will avoid duplicate hits and not screw up caches? | = Hardware Requirements = | ||
TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do/ | == Speculative Requirements == | ||
The following are a speculative list of machines required. Operations has NOT signed off or agreed to this list. Please refer to Operations for the definitive list of required hardware. | |||
* Campaign Database | |||
** A pair of relational database machines. <br> | |||
Due to the heavy index use, recommend a master/client so that master writes do not impact client reads. | |||
* Campaign request serving web heads<br> | |||
(TODO: Need to run perf. tests to see RpS of system) | |||
TODO: Need expected RpS for initial launch + expected growth) | |||
* Admin web head<br> | |||
Protected campaign management machine. | |||
(Single machine should suffice) | |||
All data logging is being done via Metlog and should require no additional hardware. | |||
= Issues and Concerns = | |||
* TODO: which redirect code will avoid duplicate hits and not screw up caches? | |||
* TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do/ | |||