跟读练习: What Is REST API? Examples And How To Use It: Crash Course System Design #3 - 通过视频学习英语口语
选择练习模式
每种模式都会打开全屏练习室。
65 句
如果句子过短或过长，请点击 Edit 进行调整。
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
Top 5 Redis Use Cases
Daily ConversationUniversity Students
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C12
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Daily ConversationUniversity StudentsWorking Adults
C17
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Daily ConversationUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Daily ConversationUniversity StudentsWorking Adults
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C16
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C13
What is API Gateway?
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
✨ 推荐视频
B21
13 句
What is an API?
Daily ConversationUniversity StudentsWorking Adults
C1231 句
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C1155 句
Every Hardware Protocol Explained Simply in 10 Minutes!
Daily ConversationUniversity StudentsWorking Adults
C11
114 句
Design a File Upload Service Like a Senior Engineer
Daily ConversationUniversity StudentsWorking Adults
C14
239 句
My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It
Daily ConversationUniversity StudentsWorking Adults
C13
9 句
Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign
Daily ConversationUniversity StudentsWorking Adults
C1204 句
Prompt Engineering - Guidelines
Daily ConversationUniversity StudentsWorking Adults
C11
158 句
OWASP Top 10 Explained
Daily ConversationUniversity StudentsWorking Adults
C11
180 句
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C12
102 句
What is Docker? Docker container concept explained || Docker Tutorial 1
Daily ConversationUniversity StudentsWorking Adults
B21
64 句
What is Python? Why Python is So Popular?
Daily ConversationUniversity StudentsWorking Adults
本课的词汇与口语要点
这段视频共有 65 个句子、753 个单词可供跟读。 讲话部分时长为 5:11。 说话人语速平稳，每分钟约 145 个词，很适合跟读。 只有 78% 的单词属于英语最常用的 3,000 词，词汇难度较高。
视频中的重点词汇
视频中 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/ | 簽署 /签署 |
| offset 名词 | /ˈɔf.sɛt/ | 补偿, 抵销 |
视频中出现的短语动词
| 单词 | 释义 |
|---|---|
| check out 动词 | 退房 |
需要注意的发音
说话人用了 4 次缩略和弱读形式，例如 we'll, don't, we'd。请按听到的简短形式来说。
- “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) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。