Pratique du Shadowing: What Are Microservices Really All About? (And When Not To Use It) - 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.

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

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
Top 5 Redis Use CasesC1
2

Top 5 Redis Use Cases

Daily ConversationUniversity Students
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 fast?C1
1

System Design: Why is Kafka fast?

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

Kubernetes Explained in 6 Minutes | k8s Architecture

Business EnglishUniversity StudentsWorking Adults
System Design: Why is Kafka Popular?C1
3

System Design: Why is Kafka Popular?

Business EnglishUniversity StudentsWorking Adults
What is API Gateway?C1
4

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
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
FOR YOU

Vidéo recommandée

Microservices explained - the What, Why and How?C1
2
184 phrases

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 phrases

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 phrases

What is an Organization? - the Nature of Organizations

Business EnglishUniversity StudentsWorking Adults
SD91: Reliability vs ScalabilityC1
2
18 phrases

SD91: Reliability vs Scalability

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

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

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

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

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

Cloud Models - CompTIA Network+ N10-009 - 1.3

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

Everything Valuable from an MBA in 25 minutes

Business EnglishUniversity StudentsWorking Adults
System Design: How to Build an API Rate LimiterC1
2
42 phrases

System Design: How to Build an API Rate Limiter

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

Microservices with Databases can be challenging...

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

Why 95% of Android Developers Get Use Cases Wrong

Business EnglishUniversity StudentsWorking Adults

Vocabulaire et conseils d’expression pour cette leçon

Cette leçon d’expression orale de niveau C1 s’appuie sur la vidéo « What Are Microservices Really All About? ». Les mots qui reviennent le plus souvent : microservice, architecture, database, component, Api. Cette vidéo contient 49 phrases et 607 mots à répéter en shadowing. La partie parlée dure 4:35. Le locuteur parle à un rythme régulier d’environ 133 mots par minute, confortable pour le shadowing. Seuls 71 % des mots font partie des 3 000 mots les plus courants en anglais, le vocabulaire est donc exigeant.

Vocabulaire clé de cette vidéo

Les 15 mots les plus avancés de la vidéo, avec leur prononciation et leur sens :

MotPrononciationSens
radius nom/ˈɹeɪ.di.əs/radius
independently adverbe/ˌɪndɪˈpɛndəntli/indépendamment
dedicate verbe/ˈdɛdɪˌkeɪt/consacrer, vouer
loosely adverbe/ˈluːsli/sans serrer
registry nom/ˈɹɛd͡ʒɪstɹi/enregistrement
startup nom/ˈstɑɹtˌʌp/mise en route, mise en train
incoming adjectif/ˈɪnˌkʌmɪŋ/entrant
flexibility nom/ˌflɛksɪˈbɪlɪti/souplesse, flexibilité
authentication nom/ɔːˌθɛntɪˈkeɪʃn̩/certification
compose verbe/kəmˈpəʊz/composer
drawback nom/ˈdɹɔˌbæk/inconvénient, désavantage
manageable adjectif/ˈmænəd͡ʒəb(ə)l/maniable, gérable
monolithic adjectif/ˌmɑ.nəˈlɪθ.ɪk/monolithique
scalable adjectif/ˈskeɪ.lə.bl̩/extensible, évolutif
schema nom/ˈskiːmə/schéma

Les verbes à particule que vous entendrez

MotSens
break up verberompre, couper
check out verbemater, regarder
go down verbedescendre
wrap up verbeemballer

Prononciation à surveiller

  • Les sons « th »: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
  • Les sons « sh » et « zh »: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, referential /ɹɛfəˈɹɛnʃəl/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, isolation /ˌaɪsəˈleɪʃən/
  • Mots longs — placez bien l’accent: 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/

Les sons difficiles pour les francophones :

  • /tʃ/ et /dʒ/ — à ne pas adoucir en « ch » et « j »: registry /ˈɹɛd͡ʒɪstɹi/, manageable /ˈmænəd͡ʒəb(ə)l/
  • /r/ anglais — langue recourbée, sans frotter la gorge: radius /ˈɹeɪ.di.əs/, registry /ˈɹɛd͡ʒɪstɹi/, startup /ˈstɑɹtˌʌp/, drawback /ˈdɹɔˌbæk/, migrate /maɪˈɡɹeɪ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 radius, independently, dedicate.

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 →