シャドーイング練習: 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
1
Cache Systems Every Developer Should Know
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です。 話す速さは1分あたり約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̩/ | 同一の, そっくりの |
| implement 動詞 | /ˈɪmpləmənt/ | 実行する, 実現する |
| interact 動詞 | /ɪn.təˈɹækt/ | 相互作用する, 相呼応する |
| subscribe 動詞 | /səbˈskɹaɪb/ | 購読する |
| organize 動詞 | /ˈɔɹɡənaɪz/ | 組織する |
動画に出てくる句動詞
| 単語 | 意味 |
|---|---|
| check out 動詞 | 試験する, 検査する |
注意したい発音
話し手は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スピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。