Shadowing Practice: What Are Microservices Really All About? (And When Not To Use It) - Learn English Speaking with Video
Kies een oefenmodus
Elke modus opent een volledig scherm oefenruimte.
49 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
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.
App downloaden
Alles wat je nodig hebt om vloeiend te spreken
AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt
Zelfde Kanaal
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
Aanbevolen Video
C12
184 zinnen
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C11
120 zinnen
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C11
43 zinnen
What is an Organization? - the Nature of Organizations
Business EnglishUniversity StudentsWorking Adults
C12
18 zinnen
SD91: Reliability vs Scalability
Business EnglishUniversity StudentsWorking Adults
C12
210 zinnen
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C11
309 zinnen
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C12
51 zinnen
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C1480 zinnen
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
C12
42 zinnen
System Design: How to Build an API Rate Limiter
Business EnglishUniversity StudentsWorking Adults
C12
279 zinnen
Microservices with Databases can be challenging...
Daily ConversationUniversity StudentsWorking Adults
C12
78 zinnen
Why 95% of Android Developers Get Use Cases Wrong
Business EnglishUniversity StudentsWorking Adults
Woordenschat en spreektips bij deze les
Deze spreekles op niveau C1 is gebaseerd op de video “What Are Microservices Really All About?”. Deze woorden komen het vaakst terug: microservice, architecture, database, component, Api. Deze video bevat 49 zinnen en 607 woorden om na te spreken. Het gesproken deel duurt 4:35. De spreker praat in een gelijkmatig tempo van ongeveer 133 woorden per minuut, prettig om te shadowen. Slechts 71% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
De 15 moeilijkste woorden uit de video, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| radius zelfstandig naamwoord | /ˈɹeɪ.di.əs/ | spaakbeen, radius |
| independently bijwoord | /ˌɪndɪˈpɛndəntli/ | onafhankelijk |
| deploy werkwoord | /dɪˈplɔɪ/ | uitrollen |
| dedicate werkwoord | /ˈdɛdɪˌkeɪt/ | inwijden, wijden |
| loosely bijwoord | /ˈluːsli/ | ruim |
| startup zelfstandig naamwoord | /ˈstɑɹtˌʌp/ | opstart, opstarting |
| authentication zelfstandig naamwoord | /ɔːˌθɛntɪˈkeɪʃn̩/ | authenticatie, authentificatie |
| compose werkwoord | /kəmˈpəʊz/ | samenstellen |
| manageable bijvoeglijk naamwoord | /ˈmænəd͡ʒəb(ə)l/ | beheerbaar, beheersbaar |
| migrate werkwoord | /maɪˈɡɹeɪt/ | migreren |
| monolithic bijvoeglijk naamwoord | /ˌmɑ.nəˈlɪθ.ɪk/ | monolithisch |
| scalable bijvoeglijk naamwoord | /ˈskeɪ.lə.bl̩/ | klimbaar, beklimbaar |
| correspond werkwoord | /ˌkoɹəˈspɑnd/ | corresponderen |
| defect zelfstandig naamwoord | /ˈdiːfɛkt/ | gebrek, mankement |
| authorization zelfstandig naamwoord | /ˌɔːθəɹaɪˈzeɪʃən/ | machtiging, volmacht |
Phrasal verbs die je zult horen
| Woord | Betekenis |
|---|---|
| check out werkwoord | onderzoeken |
| go down werkwoord | afdalen |
| wrap up werkwoord | inpakken, omhullen |
Uitspraak om op te letten
- De “th”-klanken: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- De klanken “sh” en “zh”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, referential /ɹɛfəˈɹɛnʃəl/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, isolation /ˌaɪsəˈleɪʃən/
- Lange woorden — let op de klemtoon: 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/
Klanken die Nederlandstaligen lastig vinden:
- Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: compose /kəmˈpəʊz/, correspond /ˌkoɹəˈspɑnd/, overhead /ˈəʊvəˌhɛd/, subscribe /səbˈskɹaɪb/
- /æ/ — opener dan de Nederlandse “e”: drawback /ˈdɹɔˌbæk/, manageable /ˈmænəd͡ʒəb(ə)l/, invaluable /ɪnˈvælju(ə)bl̩/
Zo oefen je met deze video
- Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
- Spreek zin voor zin na op normale snelheid en herhaal elke zin tot je ritme gelijk is aan dat van de spreker.
- Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als radius, independently, deploy.
Wat is de Shadowing-techniek?
Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.