쉐도잉 연습: Build a Real-Time Leaderboard on AWS with DynamoDB - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
Did you know that every match weekend, millions of people playing fantasy soccer get re-ranked within minutes of the final whistle?
2
Your striker scores twice, and before the highlights even air, your rank has jumped thousands of places.
3
Think about what that takes.
4
Millions of scores, reshuffled again and again, always in perfect order.
5
Ask any engineer how, and you'll get one word back.
6
Redis.
7
A cash to babysit A cluster to pay for One more thing that can fall over at 2 in the morning
8
We're skipping all of it Today, we build a real-time leaderboard on AWS where the database does the ranking itself Live boards,
9
daily and weekly rankings percentiles,
10
history and the entire ranking engine is one clever sort key We'll walk the diagram piece by piece and at the end,
11
there's a free, hands-on lab where you build every bit of it yourself.
12
Let's start with the hard part.
13
A leaderboard has one job that's harder than it looks, keeping thousands of scores in order all the time.
14
Sort them on every page load, and you're resorting the same data thousands of times a second, slow and expensive.
15
The trick is to never sort at read time at all.
16
So we store every score in Amazon DynamoDB, a serverless database that keeps rows physically ordered by their sort key.
17
Ordered ascending, smallest first.
18
Which is exactly the wrong direction for a leaderboard.
19
So we flip the scores upside down.
20
When a player scores 4,000, we subtract it from a fixed ceiling, 6 nines, and store the result as a sort key.
21
Now, the best player has the smallest key, and ascending order becomes highest score first.
22
Two small details make it bulletproof.
23
We pad the number with zeros so it sorts correctly as text.
24
And we glue the player's ID onto the end, so two identical scores can never collide.
25
The table itself is keyed by player.
26
One row per player, per board.
27
So updating your score is a single write.
28
Then we add a global secondary index.
29
A second, automatically maintained view of the same data, grouped by board and sorted by that inverted score.
30
That index is the leaderboard Read it top-down, and the ranking is already done The live board never stops moving, though The moment scores change,
31
yesterday's top 10 is gone forever So we add a second,
32
smaller table for history A snapshot table that freezes the top 50 Who ranked where,
33
at what moment Before a single line of code touches these tables, we decide who's allowed to That's IAM,
34
one execution role, shared by every function we're about to build With exactly two abilities Access to our tables,
35
and permission to write logs Five functions, same job description One role covers them all
36
Now the backend Five AWS Lambda functions Small pieces of Python that only run when called, and cost nothing in between
37
Each one does a single job The first takes score submissions
38
It writes your score to three boards at once The all-time board, today's daily board, and this week's weekly board
39
And it plays fair It only overwrites your old score if the new one is higher The second reads the board
40
One query against that inverted index, the top 25 rows, stamped rank 1 through 25
41
A few milliseconds and no sorting anywhere The third answers the question every player actually cares about Where do you rank?
42
It counts how many players sit above you in the index Adds one, and that's your rank
43
Turn that into a percentile against the whole board Because top 8% sounds a lot better than rank 200.
44
The fourth is the historian.
45
On request, it copies the current top 50 into the snapshot table, stamped with the moment it was taken.
46
And the fifth works for us.
47
A simulator that invents dozens of players, names, countries, scores, so we can test the system under load without recruiting real gamers.
48
It batch writes up to 90 rows in one shot More than Lambda's default 3 second timeout can survive
49
So we raise its timeout to 10 Five functions, but a browser can't call a Lambda directly So we put Amazon API Gateway in front
50
A REST API with five routes Submit a score, read the board, check a player,
51
take a snapshot, run the simulator Each route uses proxy integration The whole HTTP request goes straight to the function,
52
and the function shapes the whole response.
53
And every route allows cores, cross-origin requests, because our dashboard will live at a different address than the API,
54
and browsers block that unless the API explicitly allows it.
55
Deploy it to a production stage, and the whole backend sits behind one public URL.
56
Last piece, something for humans One small EC2 instance running Ubuntu With two doors open Web traffic for visitors,
57
SSH for us On it,
58
Nginx A web server built to hand out static files fast Serving a one-page dashboard A tiny config file tells
59
that page the backend's URL No framework,
60
no build step One HTML file and Nginx And quietly watching all of it CloudWatch.
61
Every one of the five functions streams its logs there.
62
That's the second half of the role we created.
63
When a score doesn't show up, that's the first place we look.
64
Now the payoff.
65
Open the instances public IP in a browser.
66
The dashboard loads.
67
Empty.
68
Click Seed Data, and the simulator floods the table.
69
Refresh.
70
There's the board.
71
Sorted top to bottom, avatars, country flags, the query time on screen reading just milliseconds.
72
Flip to daily.
73
Weekly.
74
Click a player.
75
Rank, percentile, games played.
76
No cache to warm, no cluster to babysit The database never sorted anything The scores were born sorted
77
Step back and count the pieces
78
Two DynamoDB tables A live board that sorts itself And one for history One shared IAM role Five Lambda functions Submit,
79
query, stats, snapshot, simulate One API gateway front door with five routes One EC2 instance serving the dashboard,
80
and CloudWatch logging every run.
81
And when nobody's playing, the serverless half costs nothing.
82
Functions and tables bill by use, not by the hour.
83
You've watched it come together on a diagram, but this design really sticks the moment the board lights up in your own browser, running on your own build.
84
So we made that free.
85
Two kinds of hands-on labs.
86
First, five mini labs.
87
IAM, DynamoDB, Lambda, API Gateway, and EC2.
88
Each a short, focused rep on one service from this video.
89
Then the capstone, a real AWS account where you build this exact system, the role, the two tables with the inverted index,
90
all five functions, the five API routes, the dashboard.
91
Then seed it and watch your own leaderboard sort itself.
92
The links are below.
93
If this one clicked, subscribe.
94
This video is part of a free AWS Crash Course, and more builds like it are on the way.
95
Tell us in the comments which system you want us to design next.
96
See you in the next one.
📺 같은 채널
✨ 추천 영상
C11
108 문장
How I Learned Procedural Generation
Business EnglishUniversity StudentsWorking Adults
C17
67 문장
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
B21
169 문장
Can This Vibe Coder Beat a Senior Developer?
Business EnglishUniversity StudentsWorking Adults
C11
177 문장
Mini Project - Implementing a Simple Web Identity Federation Application
Business EnglishUniversity StudentsWorking Adults
B23
189 문장
I watched 1170 minutes of Alonso's Chelsea. It's Time To Be Honest About His Tactics
Business EnglishUniversity StudentsWorking Adults
C11
190 문장
Trading Strategist: The Prop Firm Edge Isn't Your Strategy, It's How You Manage The Accounts!
Business EnglishUniversity StudentsWorking Adults
B2131 문장
what chess does to your brain
Business EnglishUniversity StudentsWorking Adults
B22
188 문장
Dot Plots: How to Actually See What Your Users Are Doing
Business EnglishUniversity StudentsWorking Adults
C11
689 문장
Database Sharding! Designing Data-Intensive Applications chapter 6
Business EnglishUniversity StudentsWorking Adults
C12
195 문장
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
C15
106 문장
A Career in IT
Business EnglishUniversity StudentsWorking Adults
이 레슨을 통해 배울 것
이번 영상은 AWS와 DynamoDB로 실시간 리더보드를 만드는 내용입니다. 기술 용어가 많고 빠르게 진행되지만, 영어 회화 연습에 좋은 기회입니다. 특히 기술적 설명을 들으면서 발음, 리듬, 강세를 연습할 수 있어요. shadow speech 기법을 사용해 영상의 대화를 따라하기면, 복잡한 내용도 자연스럽게 말할 수 있게 될 거예요.
핵심 어휘와 구문
- Leaderboard: 리더보드(순위표). "Real-time leaderboard"는 실시간 순위표를 뜻해요.
- Serverless: 서버리스. "Serverless database"는 서버 관리가 필요 없는 데이터베이스입니다.
- Sort key: 정렬 키. 데이터를 정렬하는 데 사용되는 키워드예요.
- Lambda functions: 람다 함수. AWS의 서버리스 컴퓨팅 서비스로, 특정 이벤트에 반응해 실행됩니다.
- API Gateway: API 게이트웨이. 클라이언트와 서버 간의 통신을 관리하는 서비스예요.
연습 팁: Shadowing을 잘 하는 방법
이 영상은 기술 설명이 많아 속도가 빠르고 용어가 복잡해요. shadowing을 할 때는 먼저 영상을 0.75배 속도로 듣고 따라해보세요. 강세가 있는 단어(예: "DynamoDB", "Lambda")를 집중해서 발음하고, 문장의 리듬을 따라가는 것이 중요해요. 특히 "The trick is to never sort at read time at all"처럼 긴 문장은 구간별로 나눠서 연습하세요. shadowing site를 이용해 자신의 발음을 녹음하고 원본과 비교해보면, 어느 부분이 부족한지 알 수 있어요. IELTS 스피킹 준비에도 이 방법이 효과적이에요. 매일 10분씩 연습하면, 영어 회화 실력이 눈에 띄게 향상될 거예요.
이 영상의 문법
화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.
| 문형 | 영상 속 표현 |
|---|---|
| 수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점 | is keyed · is already done · was taken |
| 현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때 | has jumped · You've watched |
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.