쉐도잉 연습: What Is REST API? Examples And How To Use It: Crash Course System Design #3 - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
REST is the most common communication standard between computers over the internet.
2
What is it?
3
Why is it so popular?
4
Let's take a look.
5
API stands for Application Programming Interface.
6
It is a way for two computers to talk to each other.
7
The common API standard used by most mobile and web applications to talk to the servers is called REST.
8
It stands for Representational State Transfer.
9
It is a mouthful.
10
What does that mean?
11
REST is not a specification.
12
It is a loose set of rules that has been the common standard for building web APIs since the early 2000s.
13
An API that follows the REST standard is called a RESTful API.
14
Some real-life examples are Twilio, Stripe, and Google Maps.
15
Let's look at the basics of REST.
16
A RESTful API organizes resources into a set of unique URIs or Uniform Resource Identifiers.
17
The URIs differentiate different types of resources on a server.
18
Here are some examples.
19
The resources should be grouped by noun and not verb.
20
An API to get all products should be slash products and not slash get all products.
21
A client interacts with a resource by making a request to the endpoint for the resource over HTTP.
22
The request has a very specific format as shown here.
23
The line contains a URI for the resource we'd like to access.
24
The URI is preceded by an XGTP verb, which tells the server what we want to do with the resource.
25
A POST request means we want to create a new resource.
26
A GET means we want to read the data about an existing resource.
27
A PUT is for updating an existing resource.
28
A DELETE is for removing an existing resource.
29
You might have heard the acronym CRUD.
30
This is what it stands for.
31
In the body of these requests, there could be an optional HTTP request body that contains a custom payload of data, usually encoded in JSON.
32
The server receives the request, processes it, and formats a result into a response.
33
The first line of the response contains the HTTP status code to tell the client what happened to the request.
34
A well implemented RESTful API returns proper HTTP status codes.
35
The 200 level codes mean the request was successful.
36
The 400 level codes mean something was wrong with our request.
37
For example, the request contained incorrect syntax.
38
At the 500 level, it means something ran wrong at the server level.
39
For example, the service was unavailable.
40
A well-behaved client could choose to retry a fail request with a 500 level status quo.
41
We said could choose to retry because some actions are not idempotent and those require extra care when retrying.
42
When an API is idempotent, making multiple identical requests has the same effect as making a single request.
43
This is usually not the case for a post request to create a new resource.
44
The response body is optional and could contain the data payload and is usually formatted in JSON.
45
There's a critical attribute of REST that is worth discussing more.
46
A REST implementation should be stateless.
47
It means the two parties don't need to store any information about each other, and every request and response is independent from all others.
48
This leads to web applications that are easy to scale and well-behaved.
49
There are two final points to discuss to round out a well-behaved RESTful API.
50
If an API endpoint returns a huge amount of data, use pagination.
51
A common pagination scheme uses limit and offset as parameters.
52
Here is an example.
53
If they are not specified, the server should assume sensible default values.
54
Lastly, versioning of an API is very important.
55
allows an implementation to provide backward compatibility so that if we introduce breaking changes from one version to another,
56
consumers can get enough time to move to the next version.
57
There are many ways to version an API.
58
The most straightforward is to prefix the version before the resource on the URI.
59
For instance, like this.
60
Restful API is simple and effective when applied sensibly.
61
It may not be the best choice for all companies, but it is simple and good enough, and that's why it is so widely used.
62
There are other popular API options like GraphQL and GRPC.
63
We'll discuss those and compare them in separate videos.
64
If you would like to learn more about system design, check out our books and weekly newsletter.
65
Please subscribe if you learned something new thank you so much and we'll see you next time
📺 같은 채널
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C11
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Business EnglishUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Business EnglishUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Business EnglishUniversity StudentsWorking Adults
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C12
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C15
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
Business EnglishUniversity StudentsWorking Adults
C148
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
✨ 추천 영상
C11
180 문장
Your API Can’t Handle Real-World Integrations
Business EnglishUniversity StudentsWorking Adults
C12
444 문장
INTRODUCTION INTO HUMAN RESOURCES MANAGEMENT - LECTURE 01
Business EnglishUniversity StudentsWorking Adults
C12
102 문장
What is Docker? Docker container concept explained || Docker Tutorial 1
Business EnglishUniversity StudentsWorking Adults
C12
119 문장
How to Write Test Cases for Manual Testing?
Business EnglishUniversity StudentsWorking Adults
C1155 문장
Every Hardware Protocol Explained Simply in 10 Minutes!
Business EnglishUniversity StudentsWorking Adults
C1231 문장
Redis Crash Course - the What, Why and How to use Redis as your primary database
Business EnglishUniversity StudentsWorking Adults
C15
107 문장
What is NLP? Neuro Linguistic Programming
Business EnglishUniversity StudentsWorking Adults
C11
258 문장
What is Accounting ? An Introduction to Accounting.
Business EnglishUniversity StudentsWorking Adults
C12
14 문장
CS50x 2026 - Introduction
Business EnglishUniversity StudentsWorking Adults
C12
153 문장
S3 Speech1 short
Business EnglishUniversity StudentsWorking Adults
이 레슨의 어휘와 말하기 포인트
이 영상에는 섀도잉할 문장 65개와 단어 753개가 있습니다. 말하는 구간의 길이는 5:11입니다. 화자는 분당 약 145단어의 일정한 속도로 말해서 섀도잉하기에 편한 속도입니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 78%뿐이라 어휘가 어려운 편입니다.
이 영상의 핵심 어휘
영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| resource 명사 | /ɹɪˈzɔːs/ | 자원 |
| server 명사 | /ˈsɝvɚ/ | 서버, 봉사기 |
| format 명사 | /ˈfɔːɹ.mæt/ | 포맷 |
| behave 동사 | /bɪˈheɪv/ | 처신하다, 행동하다 |
| implementation 명사 | /ˌɪmplɪmənˈteɪʃən/ | 이행 |
| verb 명사 | /vɝb/ | 동사 |
| compare 동사 | /kəmˈpɛɚ/ | 비교하다, 비유하다 |
| custom 명사 | /ˈkʌstəm/ | 습관, 풍속 |
| introduce 동사 | /ˌɪntɹəˈdus/ | 소개(紹介)하다 |
| default 명사 | /dɪˈfɔlt/ | 디폴트 |
| identical 형용사 | /ɪˈdɛntɪkl̩/ | 동일한, 똑같은 |
| subscribe 동사 | /səbˈskɹaɪb/ | 구독하다 |
| organize 동사 | /ˈɔɹɡənaɪz/ | 조직하다 |
| incorrect 형용사 | /ˌɪn.kəˈɹɛkt/ | 그른, 잘못된 |
| attribute 명사 | /ˈæt.ɹɪˌbjut/ | 속성, 특질 |
주의할 발음
화자는 we'll, don't, we'd 같은 축약형과 약화된 형태를 4번 사용합니다. 들리는 대로 짧게 발음하세요.
- “sh”와 “zh” 소리: implementation /ˌɪmplɪmənˈteɪʃən/, optional /ˈɑp.ʃə.nəl/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/, pagination /ˌpæd͡ʒəˈneɪʃən/
- 긴 단어 — 강세 위치에 주의: implementation /ˌɪmplɪmənˈteɪʃən/, unavailable /ˌʌnəˈveɪləbəl/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/, compatibility /kəmˌpætəˈbɪlɪti/, parameter /pəˈɹæm.ə.tɚ/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
- 자신의 목소리를 녹음해 원본과 비교하고, resource, server, format 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.