From e7cb0063599174eb4be39bd09c28aa5f35e6fbd8 Mon Sep 17 00:00:00 2001 From: Huanyi Chen Date: Sun, 17 Mar 2024 15:57:58 -0400 Subject: [PATCH] Prepare L34 & L35 flip note --- lectures/flipped/L34.md | 7 +++++++ lectures/flipped/L35.md | 10 +++++++++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/lectures/flipped/L34.md b/lectures/flipped/L34.md index c2cd6377..09037670 100644 --- a/lectures/flipped/L34.md +++ b/lectures/flipped/L34.md @@ -6,6 +6,13 @@ This is a bit of a weird lecture in person since the content is a video. We have some exercises though. Context: how do you scale up web services from 1 user to 11+ million users, with stops along the way. +## Intro + +The first episode of the YouTube series is a good introduction: + + +Which I found from + ## Scalability Now, onto actual questions about practical scaling and AWS. diff --git a/lectures/flipped/L35.md b/lectures/flipped/L35.md index 85ec1f6d..ca54409c 100644 --- a/lectures/flipped/L35.md +++ b/lectures/flipped/L35.md @@ -3,7 +3,8 @@ ## Roadmap I thought of 3 potential exercises in this DevOps space. We can look at them and -decide which order to do them in (and how many to do). +decide which order to do them in (and how many to do). The first two are based +on L34 note. ## Naming @@ -23,6 +24,13 @@ I figured out how to use GitHub Actions to compile the TeX files automatically. Probably the easiest CI thing is to run test cases for a project automatically. Pick some Java project and set up a GitHub action for it. +## A Real Incident + +We can talk about how it can be avoided: + + + + # After-action report, plam, 3 Apr 2023 Did the naming exercise. Did not do the other exercises. Instead, we