Pratique du Shadowing: What Is REST API? Examples And How To Use It: Crash Course System Design #3 - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Chaque mode ouvre une salle d'entraînement en plein écran.

65 phrases
Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.
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

Télécharger l'application

Tout pour parler couramment

Prononciation IAChaque phrase notée
Phonétique (IPA)Maîtrisez chaque son
VocabulaireEnrichissez votre lexique
Jeu de vocabulaireApprenez en jouant
Scanner le QR
Scanner le QR
Download on theApp StoreGet it onGoogle Play
📺 Même chaîne
The Secret Sauce Behind NoSQL: LSM TreeC1
1

The Secret Sauce Behind NoSQL: LSM Tree

Daily ConversationUniversity StudentsWorking Adults
Proxy vs Reverse Proxy (Real-world Examples)C1
3

Proxy vs Reverse Proxy (Real-world Examples)

Daily ConversationUniversity StudentsWorking Adults
Cache Systems Every Developer Should KnowC1
2

Cache Systems Every Developer Should Know

Daily ConversationUniversity StudentsWorking Adults
System Design Was HARD - Until You Knew the Trade-OffsC1
3

System Design Was HARD - Until You Knew the Trade-Offs

Daily ConversationUniversity StudentsWorking Adults
8 Most Important System Design Concepts You Should KnowC1
7

8 Most Important System Design Concepts You Should Know

Daily ConversationUniversity StudentsWorking Adults
Everything You Need to Know About DNS: Crash Course System Design #4C1
3

Everything You Need to Know About DNS: Crash Course System Design #4

Daily ConversationUniversity StudentsWorking Adults
CAP Theorem SimplifiedC1
2

CAP Theorem Simplified

Daily ConversationUniversity StudentsWorking Adults
System Design: Why is Kafka Popular?C1
2

System Design: Why is Kafka Popular?

Business EnglishUniversity StudentsWorking Adults
What Are Microservices Really All About? (And When Not To Use It)C1
5

What Are Microservices Really All About? (And When Not To Use It)

Business EnglishUniversity StudentsWorking Adults
System Design: Why is Kafka fast?C1
1

System Design: Why is Kafka fast?

Business EnglishUniversity StudentsWorking Adults
What is API Gateway?C1
3

What is API Gateway?

Business EnglishUniversity StudentsWorking Adults
10+ Key Memory & Storage Systems: Crash Course System Design #5C1
2

10+ Key Memory & Storage Systems: Crash Course System Design #5

University StudentsWorking Adults
What Is Redis Really About? Why Is It So Popular?C2
4

What Is Redis Really About? Why Is It So Popular?

Business EnglishUniversity StudentsWorking Adults
Kubernetes Explained in 6 Minutes | k8s ArchitectureC1
48

Kubernetes Explained in 6 Minutes | k8s Architecture

Business EnglishUniversity StudentsWorking Adults
How Does a URL Shortener Work?C1
3

How Does a URL Shortener Work?

Business EnglishInterview EnglishUniversity Students
How Git Works: Explained in 4 MinutesB2

How Git Works: Explained in 4 Minutes

Business EnglishUniversity StudentsWorking Adults
✨ Vidéo recommandée
What is an API?B2
1
13 phrases

What is an API?

Daily ConversationUniversity StudentsWorking Adults
Redis Crash Course - the What, Why and How to use Redis as your primary databaseC1
231 phrases

Redis Crash Course - the What, Why and How to use Redis as your primary database

Daily ConversationUniversity StudentsWorking Adults
Every Hardware Protocol Explained Simply in 10 Minutes!C1
155 phrases

Every Hardware Protocol Explained Simply in 10 Minutes!

Daily ConversationUniversity StudentsWorking Adults
Design a File Upload Service Like a Senior EngineerC1
1
114 phrases

Design a File Upload Service Like a Senior Engineer

Daily ConversationUniversity StudentsWorking Adults
My 4.9-Star iOS App Is Actually a Website: Here’s How I Built ItC1
4
239 phrases

My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It

Daily ConversationUniversity StudentsWorking Adults
Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesignC1
3
9 phrases

Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign

Daily ConversationUniversity StudentsWorking Adults
Prompt Engineering - GuidelinesC1
204 phrases

Prompt Engineering - Guidelines

Daily ConversationUniversity StudentsWorking Adults
OWASP Top 10 ExplainedC1
1
158 phrases

OWASP Top 10 Explained

Daily ConversationUniversity StudentsWorking Adults
Armchair Architects: Resiliency in the Cloud – Core PatternsC1
1
180 phrases

Armchair Architects: Resiliency in the Cloud – Core Patterns

Daily ConversationUniversity StudentsWorking Adults
What is Docker? Docker container concept explained || Docker Tutorial 1C1
2
102 phrases

What is Docker? Docker container concept explained || Docker Tutorial 1

Daily ConversationUniversity StudentsWorking Adults
S3 Speech1 shortC1
2
153 phrases

S3 Speech1 short

Daily ConversationUniversity StudentsWorking Adults

Vocabulaire et conseils d’expression pour cette leçon

Cette vidéo contient 65 phrases et 753 mots à répéter en shadowing. La partie parlée dure 5:11. Le locuteur parle à un rythme régulier d’environ 145 mots par minute, confortable pour le shadowing. Seuls 78 % des mots font partie des 3 000 mots les plus courants en anglais, le vocabulaire est donc exigeant.

Vocabulaire clé de cette vidéo

15 mots de la vidéo à retenir, avec leur prononciation et leur sens :

MotPrononciationSens
resource nom/ɹɪˈzɔːs/ressource
server nom/ˈsɝvɚ/serveur
format nom/ˈfɔːɹ.mæt/format
behave verbe/bɪˈheɪv/se comporter
implementation nom/ˌɪmplɪmənˈteɪʃən/mise en œuvre
optional adjectif/ˈɑp.ʃə.nəl/optionnel, facultatif
verb nom/vɝb/verbe
compare verbe/kəmˈpɛɚ/comparer
custom nom/ˈkʌstəm/coutume
introduce verbe/ˌɪntɹəˈdus/présenter
default nom/dɪˈfɔlt/défaut, non-respect
identical adjectif/ɪˈdɛntɪkl̩/identique
implement verbe/ˈɪmpləmənt/appliquer, exécuter
interact verbe/ɪn.təˈɹækt/interagir
subscribe verbe/səbˈskɹaɪb/abonner, s'abonner

Les verbes à particule que vous entendrez

MotSens
check out verbemater, regarder

Prononciation à surveiller

Le locuteur utilise 4 contractions et formes réduites, comme we'll, don't, we'd. Prononcez-les sous leur forme courte, telles que vous les entendez.

  • Les sons « sh » et « zh »: implementation /ˌɪmplɪmənˈteɪʃən/, optional /ˈɑp.ʃə.nəl/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/, pagination /ˌpæd͡ʒəˈneɪʃən/
  • Mots longs — placez bien l’accent: 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ɚ/

Comment s’entraîner avec cette vidéo

  1. Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
  2. Répétez phrase par phrase à vitesse normale, en reprenant chacune jusqu’à ce que votre rythme corresponde à celui du locuteur.
  3. Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme resource, server, format.

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Technique du shadowing : lire le guide complet étape par étape →