Shadowing Practice: What Is REST API? Examples And How To Use It: Crash Course System Design #3 - Learn English Speaking with Video

Creando lección...
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

Vocabulario y notas de pronunciación para esta lección

Este vídeo tiene 65 frases y 753 palabras para practicar shadowing. La parte hablada dura 5:11. El hablante mantiene un ritmo constante de unas 145 palabras por minuto, cómodo para el shadowing. Solo el 78 % de las palabras está entre las 3.000 más comunes del inglés, por lo que el vocabulario es exigente.

Vocabulario clave de este vídeo

15 palabras del vídeo que vale la pena aprender, con su pronunciación y significado:

PalabraPronunciaciónSignificado
resource sustantivo/ɹɪˈzɔːs/recurso
server sustantivo/ˈsɝvɚ/servidor
format sustantivo/ˈfɔːɹ.mæt/formato
behave verbo/bɪˈheɪv/portarse
implementation sustantivo/ˌɪmplɪmənˈteɪʃən/puesta en práctica, implementación
optional adjetivo/ˈɑp.ʃə.nəl/opcional
verb sustantivo/vɝb/verbo
compare verbo/kəmˈpɛɚ/comparar, parangonar
custom sustantivo/ˈkʌstəm/costumbre, usanza
introduce verbo/ˌɪntɹəˈdus/presentar
default sustantivo/dɪˈfɔlt/mora, default
identical adjetivo/ɪˈdɛntɪkl̩/idéntico, clónico
implement verbo/ˈɪmpləmənt/implementar
interact verbo/ɪn.təˈɹækt/interactuar
subscribe verbo/səbˈskɹaɪb/suscribirse, subscribirse

Phrasal verbs que vas a escuchar

PalabraSignificado
check out verboinvestigar, chequear

Pronunciación a tener en cuenta

El hablante usa 4 contracciones y formas reducidas, como we'll, don't, we'd. Dilas en su forma corta, tal como las oyes.

  • Los sonidos de “sh” y “zh”: implementation /ˌɪmplɪmənˈteɪʃən/, optional /ˈɑp.ʃə.nəl/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/, pagination /ˌpæd͡ʒəˈneɪʃən/
  • Palabras largas — cuida el acento: 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ɚ/

Cómo practicar con este vídeo

  1. Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
  2. Haz shadowing frase por frase a velocidad normal, repitiendo cada una hasta que tu ritmo coincida con el del hablante.
  3. Grábate y compara con el original, prestando atención a palabras como resource, server, format.

¿Qué es la Técnica de Shadowing?

Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.

Técnica de shadowing: lee la guía completa paso a paso →