Shadowing-Übung: What Are Microservices Really All About? (And When Not To Use It) - Englisch Sprechen Lernen mit Video
Übungsmodus wählen
Jeder Modus öffnet einen Übungsraum im Vollbild.
49 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
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 herunterladen
Alles, was du zum fließenden Sprechen brauchst
KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen
📺 Gleicher Kanal
C11
Top 5 Redis Use Cases
Daily ConversationUniversity Students
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
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
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C13
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
C150
Kubernetes Explained in 6 Minutes | k8s Architecture
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
✨ Empfohlenes Video
C12
184 Sätze
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C11
120 Sätze
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C11
43 Sätze
What is an Organization? - the Nature of Organizations
Business EnglishUniversity StudentsWorking Adults
C12
210 Sätze
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C11
309 Sätze
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C12
51 Sätze
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C1480 Sätze
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
C12
279 Sätze
Microservices with Databases can be challenging...
Daily ConversationUniversity StudentsWorking Adults
C12
78 Sätze
Why 95% of Android Developers Get Use Cases Wrong
Business EnglishUniversity StudentsWorking Adults
C12
195 Sätze
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
Wortschatz und Sprechhinweise zu dieser Lektion
Diese Sprechübung auf Niveau C1 basiert auf dem Video „What Are Microservices Really All About?“. Diese Wörter kommen am häufigsten vor: microservice, architecture, database, component, Api. Dieses Video enthält 49 Sätze und 607 Wörter zum Nachsprechen. Der gesprochene Teil dauert 4:35. Der Sprecher spricht gleichmäßig mit etwa 133 Wörtern pro Minute – ein angenehmes Tempo fürs Shadowing. Nur 71 % der Wörter gehören zu den 3.000 häufigsten im Englischen, der Wortschatz ist also anspruchsvoll.
Wichtiger Wortschatz in diesem Video
Die 15 anspruchsvollsten Wörter aus dem Video, mit Aussprache und Bedeutung:
| Wort | Aussprache | Bedeutung |
|---|---|---|
| radius Substantiv | /ˈɹeɪ.di.əs/ | Speiche, Radius |
| independently Adverb | /ˌɪndɪˈpɛndəntli/ | unabhängig, selbstständig |
| deploy Verb | /dɪˈplɔɪ/ | aufstellen, formieren |
| dedicate Verb | /ˈdɛdɪˌkeɪt/ | widmen |
| registry Substantiv | /ˈɹɛd͡ʒɪstɹi/ | Registratur |
| startup Substantiv | /ˈstɑɹtˌʌp/ | Inbetriebnahme |
| incoming Adjektiv | /ˈɪnˌkʌmɪŋ/ | eingehend |
| flexibility Substantiv | /ˌflɛksɪˈbɪlɪti/ | Flexibilität |
| authentication Substantiv | /ɔːˌθɛntɪˈkeɪʃn̩/ | Authentifikation |
| compose Verb | /kəmˈpəʊz/ | zusammenstellen, zusammensetzen |
| drawback Substantiv | /ˈdɹɔˌbæk/ | Nachteil, Minuspunkt |
| manageable Adjektiv | /ˈmænəd͡ʒəb(ə)l/ | handhabbar |
| migrate Verb | /maɪˈɡɹeɪt/ | migrieren |
| monolithic Adjektiv | /ˌmɑ.nəˈlɪθ.ɪk/ | monolithisch |
| scalable Adjektiv | /ˈskeɪ.lə.bl̩/ | skalierbar |
Phrasal Verbs, die du hören wirst
| Wort | Bedeutung |
|---|---|
| check out Verb | überprüfen |
| go down Verb | absteigen, hinabsteigen |
| wrap up Verb | verpacken, einpacken |
Aussprache, auf die du achten solltest
- Die „th“-Laute: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- Die Laute „sh“ und „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 Wörter – auf die Betonung achten: 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/
Laute, die Deutschsprachigen schwerfallen:
- Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: compose /kəmˈpəʊz/, correspond /ˌkoɹəˈspɑnd/, overhead /ˈəʊvəˌhɛd/, subscribe /səbˈskɹaɪb/
- /æ/ — offener als „ä“: drawback /ˈdɹɔˌbæk/, manageable /ˈmænəd͡ʒəb(ə)l/, invaluable /ɪnˈvælju(ə)bl̩/
- /dʒ/ — stimmhaft, nicht „tsch“: registry /ˈɹɛd͡ʒɪstɹi/, manageable /ˈmænəd͡ʒəb(ə)l/
So übst du mit diesem Video
- Höre dir das ganze Video einmal an, ohne zu sprechen, und notiere die Wörter, die du nicht kennst.
- Sprich Satz für Satz in normaler Geschwindigkeit nach und wiederhole jeden, bis dein Rhythmus zum Sprecher passt.
- Nimm dich auf und vergleiche mit dem Original; achte dabei auf Wörter wie radius, independently, deploy.
Was ist die Shadowing-Technik?
Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.