This exercise aims to learn how web application scaling is done in real world scenarios.
- Create an exercise documentation (en|de) while you are working on the tasks.
- For every task, write down your initial thoughts, assumptions, and the final outcome in full sentences. Describe the process of solving the task.
- If you are not able to solve the task, describe how you would solve it theoretically. You should still provide a step by step description from the documentation or tutorial you found.
- Provide a reference for every documentation or tutorial you used to solve a task. Paraphrase and cite correctly, please.
- Your submission should be described in at least one, but not more than three A4 pages.
Read through all tasks first. You will research how YouTube scaled its system over the years. If you are consuming one of their talks on this topic, make notes and reference the video or podcast correctly in your submission.
- Which sources did you find and use?
- What was the initial Architecture and Infrastructure of YouTube, according to your source?
- When did they decide to take special care of scaling? What were the events (at least two) that showed that YouTube has to take scaling measures?
- Explain what they did to be more resilient against high demand.
- Include a self-made diagram of YouTube's improved Architecture and Infrastructure (or some aspect of it). Add a short explanation, on what it shows. Don't forget to reference your sources, also for the content of this diagram.