Pratica di Shadowing: What Are Microservices Really All About? (And When Not To Use It) - Impara a parlare inglese con i video

Scegli una modalità di pratica

Ogni modalità apre una sala di pratica a schermo intero.

49 frasi
Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.
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.

Scarica l'app

Tutto ciò che serve per parlare fluentemente

Pronuncia con IAVoto per ogni frase
Pratica IPAPadroneggia ogni suono
VocabolarioCostruisci il tuo lessico
Gioco di vocabolarioImpara giocando
Scansiona QR
Scansiona QR
Download on theApp StoreGet it onGoogle Play
📺 Stesso Canale
Top 5 Redis Use CasesC1
1

Top 5 Redis Use Cases

Daily ConversationUniversity Students
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
What Is REST API? Examples And How To Use It: Crash Course System Design #3C1
2

What Is REST API? Examples And How To Use It: Crash Course System Design #3

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

System Design: Why is Kafka Popular?

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
✨ Video consigliato
Microservices explained - the What, Why and How?C1
2
184 frasi

Microservices explained - the What, Why and How?

Business EnglishUniversity StudentsWorking Adults
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big TableC1
1
120 frasi

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

Business EnglishUniversity StudentsWorking Adults
What is an Organization? - the Nature of OrganizationsC1
1
43 frasi

What is an Organization? - the Nature of Organizations

Business EnglishUniversity StudentsWorking Adults
What Software Architecture Should Look Like • Dave Farley • GOTO 2022C1
2
210 frasi

What Software Architecture Should Look Like • Dave Farley • GOTO 2022

Business EnglishUniversity StudentsWorking Adults
Cloud Models - CompTIA Network+ N10-009 - 1.3C1
2
51 frasi

Cloud Models - CompTIA Network+ N10-009 - 1.3

Business EnglishUniversity StudentsWorking Adults
Claude Code: The Advanced Guide (99% of Devs Skip These Features)C1
1
309 frasi

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

Business EnglishUniversity StudentsWorking Adults
Everything Valuable from an MBA in 25 minutesC1
480 frasi

Everything Valuable from an MBA in 25 minutes

Business EnglishUniversity StudentsWorking Adults
Microservices with Databases can be challenging...C1
2
279 frasi

Microservices with Databases can be challenging...

Daily ConversationUniversity StudentsWorking Adults
Why 95% of Android Developers Get Use Cases WrongC1
2
78 frasi

Why 95% of Android Developers Get Use Cases Wrong

Business EnglishUniversity StudentsWorking Adults
JavaScript Visualized - Event Loop, Web APIs, (Micro)task QueueC1
2
195 frasi

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

Business EnglishUniversity StudentsWorking Adults

Obiettivi di parlato per questo video

Questo clip aiuta a raggiungere una pietra miliare nella fluency: la capacità di esprimere concetti tecnici complessi in modo chiaro e strutturato. Ideale per chi vuole migliorare la pronuncia inglese e la pratica di conversazione in inglese, soprattutto in contesti professionali o accademici. Attraverso l'analisi di un argomento specifico come l'architettura a microservizi, si esercita a seguire un discorso logico e a riprodurre frasi con intonazione naturale.

Banca di frasi riutilizzabili

  • "enables large teams to build scalable applications" (permette a team grandi di creare applicazioni scalabili)
  • "loosely coupled services" (servizi debolmente accoppiati)
  • "blast radius of failures" (raggio d'azione dei guasti)
  • "independently deployed" (distribuito in modo indipendente)
  • "strong information hiding" (forte nascondimento delle informazioni)
  • "burden of maintaining data integrity" (fardello di mantenere l'integrità dei dati)

Correggi i tuoi punti deboli

Questo video è perfetto per lavorare sulla pronuncia di termini tecnici e sulla ritmica del discorso. Molte espressioni come "microservices architecture" o "service registry" richiedono una corretta enfasi sulle sillabe chiave. Usa il metodo del shadowing (ripetizione immediata) per imitare la velocità e l'intonazione del speaker: questo aiuta a superare la difficoltà di pronuncia di parole lunghe e a integrare frasi complesse nella tua pratica di conversazione in inglese. Un shadowing site o strumenti come shadowspeaks possono amplificare gli effetti, permettendo di confrontare la tua riproduzione con l'originale. Ricorda: la chiave è la costanza, non la perfezione!

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Tecnica dello shadowing: leggi la guida completa passo dopo passo →