Shadowing Practice: What Are Microservices Really All About? (And When Not To Use It) - Learn English Speaking with Video
Elige un modo de práctica
Cada modo abre una sala de práctica a pantalla completa.
49 oraciones
Si las oraciones son demasiado cortas o largas, haz clic en Editar para ajustarlas.
1
Microservices architecture enables large teams to build scalable applications that are composed of many loosely coupled services.
2
What does a typical microservices architecture look like, and when should we use it?
3
Let's take a look.
4
Microservices are loosely coupled.
5
Each service handles a dedicated function inside a large-scale application.
6
For example, shopping cart, billing, user profile, push notifications can all be individual microservices.
7
These functional areas are sometimes called domains.
8
Microservices communicate with each other via well-defined interfaces with small service areas.
9
The small service areas limit the blast radius of failures and defects.
10
it makes each service easier to reason about in the context of the entire application.
11
Microservices talk to one another over a combination of remote procedure calls, or RPC, event streaming, or message brokers.
12
RPC like GRPC provides faster response,
13
but the blast radius or the impact to other microservices would be larger when the service was to go down.
14
Event streaming provides better isolation between services, but they take longer to process.
15
Microservices can be independently deployed.
16
Since each service is smaller, easier to reason about, and has a smaller blast radius.
17
This gives the operators peace of mind and confidence to deploy often.
18
Microservices provide more flexibility to scale up individual microservices independently.
19
The operational flexibility is invaluable.
20
Well-architected microservices practice strong information hiding.
21
This often means breaking up a monolithic database into its logical components
22
and keeping each logical component well hidden inside its corresponding microservice.
23
By logical component, it could mean a separate schema within a database cluster or an entirely separate physical database.
24
This is an implementation detail.
25
However, one big drawback of microservices is the breaking up of the database.
26
By breaking up a database into separate logical units,
27
the database can no longer maintain foreign key relationships and enforce referential integrity between these units.
28
The burden of maintaining data integrity is now moved into the application layer.
29
Now, let's take a look at other critical components required for a successful implementation of microservices architecture.
30
A key component is an API Gateway.
31
API Gateway handles incoming requests and routes them to the relevant microservices.
32
The API Gateway relies on an identity provider service to handle the authentication and authorization
33
of each request coming through the API Gateway.
34
To locate a service to route an incoming request to, the API Gateway consults a service registry and Discovery Service.
35
Microservices register with this service registry and discover the location of other microservices through the Discovery Service.
36
There are other useful components in a microservices architecture, like monitoring and alerting, DevOps toolings for deployment and troubleshooting, for example.
37
Let's wrap up by discussing when to use microservices architecture.
38
Microservices cost money to build and operate.
39
It really only makes sense for large teams.
40
For large teams, it enables team independence.
41
Each domain or function can be independently maintained by a dedicated team.
42
In a well-designed microservices architecture, these independent teams can move fast and the blast radius of failure is well-contained.
43
Each service could be independently designed, deployed, and scaled.
44
However, the overhead of a SANG implementation is so large that it is usually not a good fit for small startups.
45
One advice for startups is to design each function in the application with a well-defined interface.
46
One day, if the business and team are growing fast, that microservices architecture starts to make sense, it will be manageable to migrate.
47
If you would like to learn more about system design, check out our books and weekly newsletter.
48
Please subscribe if you learned something new.
49
Thank you so much and we'll see you next time.
Descargar app
Todo lo que necesitas para hablar con fluidez
Pronunciación con IAEvalúa cada oración
Práctica de IPADomina cada sonido
VocabularioConstruye tu banco de palabras
Juego de vocabularioAprende mientras juegas
Mismo canal
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
C12
Top 5 Redis Use Cases
Daily ConversationUniversity Students
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
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Daily ConversationUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C150
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity StudentsWorking Adults
C13
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C14
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
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
FOR YOU
Recomendar Video
C12
184 oraciones
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C11
120 oraciones
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C11
43 oraciones
What is an Organization? - the Nature of Organizations
Business EnglishUniversity StudentsWorking Adults
C12
18 oraciones
SD91: Reliability vs Scalability
Business EnglishUniversity StudentsWorking Adults
C12
210 oraciones
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C11
309 oraciones
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C11
315 oraciones
how AI broke the SWE Career Ladder
Business EnglishInterview EnglishUniversity Students
C12
51 oraciones
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C1480 oraciones
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
C12
42 oraciones
System Design: How to Build an API Rate Limiter
Business EnglishUniversity StudentsWorking Adults
C12
279 oraciones
Microservices with Databases can be challenging...
Daily ConversationUniversity StudentsWorking Adults
Vocabulario y notas de pronunciación para esta lección
Esta lección de conversación de nivel C1 se basa en el vídeo “What Are Microservices Really All About?”. Las palabras que más se repiten: microservice, architecture, database, component, Api. Este vídeo tiene 49 frases y 607 palabras para practicar shadowing. La parte hablada dura 4:35. El hablante mantiene un ritmo constante de unas 133 palabras por minuto, cómodo para el shadowing. Solo el 71 % 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
Las 15 palabras más avanzadas del vídeo, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| radius sustantivo | /ˈɹeɪ.di.əs/ | radio |
| independently adverbio | /ˌɪndɪˈpɛndəntli/ | independientemente |
| deploy verbo | /dɪˈplɔɪ/ | desplegar |
| dedicate verbo | /ˈdɛdɪˌkeɪt/ | dedicar |
| startup sustantivo | /ˈstɑɹtˌʌp/ | arranque |
| flexibility sustantivo | /ˌflɛksɪˈbɪlɪti/ | flexibilidad |
| authentication sustantivo | /ɔːˌθɛntɪˈkeɪʃn̩/ | autenticación |
| compose verbo | /kəmˈpəʊz/ | componer |
| drawback sustantivo | /ˈdɹɔˌbæk/ | desventaja, pega |
| manageable adjetivo | /ˈmænəd͡ʒəb(ə)l/ | manejable, gestionable |
| migrate verbo | /maɪˈɡɹeɪt/ | migrar |
| monolithic adjetivo | /ˌmɑ.nəˈlɪθ.ɪk/ | monolítico |
| scalable adjetivo | /ˈskeɪ.lə.bl̩/ | escalable |
| tooling sustantivo | utillaje | |
| troubleshooting sustantivo | hallazgo de soluciones, identificación de problemas |
Phrasal verbs que vas a escuchar
| Palabra | Significado |
|---|---|
| break up verbo | separar, cisionar |
| check out verbo | investigar, chequear |
| wrap up verbo | envolver, arrebujar |
Pronunciación a tener en cuenta
- Los sonidos de “th”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- Los sonidos de “sh” y “zh”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, referential /ɹɛfəˈɹɛnʃəl/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, isolation /ˌaɪsəˈleɪʃən/
- Palabras largas — cuida el acento: independently /ˌɪndɪˈpɛndəntli/, flexibility /ˌflɛksɪˈbɪlɪti/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, manageable /ˈmænəd͡ʒəb(ə)l/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/
Sonidos difíciles para hispanohablantes:
- s + consonante al inicio — sin añadir una “e” delante: startup /ˈstɑɹtˌʌp/, scalable /ˈskeɪ.lə.bl̩/, schema /ˈskiːmə/
- /v/ — no es /b/: los dientes tocan el labio inferior: invaluable /ɪnˈvælju(ə)bl̩/, overhead /ˈəʊvəˌhɛd/
- /z/ — sonora, no /s/: compose /kəmˈpəʊz/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, newsletter /ˈn(j)uzˌlɛtɚ/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Haz shadowing frase por frase a velocidad normal, repitiendo cada una hasta que tu ritmo coincida con el del hablante.
- Grábate y compara con el original, prestando atención a palabras como radius, independently, deploy.
¿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.