Shadowing Practice: What Are Microservices Really All About? (And When Not To Use It) - Learn English Speaking with Video
Bir pratik modu seçin
Her mod tam ekran bir pratik odası açar.
49 cümleler
Cümleler çok kısa veya çok uzun ise, ayarlamak için Düzenle'ye tıklayın.
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.
Uygulamayı İndir
Akıcı konuşmak için ihtiyacınız olan her şey
AI TelaffuzHer cümleyi puanla
IPA AlıştırmasıHer sesi ustalaştır
Kelime BilgisiKelime bankanızı oluşturun
Kelime OyunuOynarken öğrenin
Aynı Kanal
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
C12
System Design: Why is Kafka Popular?
Business EnglishUniversity 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
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
Video Öner
C12
184 cümleler
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C11
120 cümleler
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C11
43 cümleler
What is an Organization? - the Nature of Organizations
Business EnglishUniversity StudentsWorking Adults
C12
210 cümleler
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C11
309 cümleler
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C12
51 cümleler
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C1480 cümleler
Everything Valuable from an MBA in 25 minutes
Business EnglishUniversity StudentsWorking Adults
C12
279 cümleler
Microservices with Databases can be challenging...
Daily ConversationUniversity StudentsWorking Adults
C12
78 cümleler
Why 95% of Android Developers Get Use Cases Wrong
Business EnglishUniversity StudentsWorking Adults
C12
195 cümleler
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu C1 seviyesindeki konuşma dersi “What Are Microservices Really All About?” videosuna dayanıyor. En çok tekrarlanan kelimeler: microservice, architecture, database, component, Api. Bu videoda gölgeleme çalışması için 49 cümle ve 607 kelime var. Konuşma bölümü 4:35 sürüyor. Konuşmacı dakikada yaklaşık 133 kelimelik dengeli bir hızla konuşuyor; gölgeleme için rahat bir tempo. Kelimelerin yalnızca %71’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığı zorlayıcı.
Bu videodaki önemli kelimeler
Videodaki en ileri düzey 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| radius isim | /ˈɹeɪ.di.əs/ | döner kemik |
| registry isim | /ˈɹɛd͡ʒɪstɹi/ | evrak dairesi |
| flexibility isim | /ˌflɛksɪˈbɪlɪti/ | esneklik, elastikiyet |
| authentication isim | /ɔːˌθɛntɪˈkeɪʃn̩/ | kimlik doğrulama, kimlik kanıtlama |
| compose fiil | /kəmˈpəʊz/ | bestelemek |
| schema isim | /ˈskiːmə/ | şema |
| defect isim | /ˈdiːfɛkt/ | eksik, kusur |
| authorization isim | /ˌɔːθəɹaɪˈzeɪʃən/ | izin, otorizasyon |
| newsletter isim | /ˈn(j)uzˌlɛtɚ/ | haber bülteni |
| broker isim | /ˈbɹoʊkɚ/ | komisyoncu, simsar |
| deployment isim | /dɪˈplɔɪmənt/ | dağıtım, teslimat |
| notification isim | /ˌnoʊtɪfɪˈkeɪʃn̩/ | bildirme, bilgilendirme |
| overhead isim | /ˈəʊvəˌhɛd/ | genel giderler |
| locate fiil | /ˈloʊˌkeɪt/ | yerleştirmek |
| cart isim | /kɑɹt/ | alışveriş arabası, kağnı |
Duyacağınız deyimsel fiiller
| Kelime | Anlam |
|---|---|
| check out fiil | gözden geçirmek |
| wrap up fiil | paketlemek, (bir şeyi) sarmak |
Dikkat edilecek telaffuzlar
- “th” sesleri: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, monolithic /ˌmɑ.nəˈlɪθ.ɪk/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- “sh” ve “zh” sesleri: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, referential /ɹɛfəˈɹɛnʃəl/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, isolation /ˌaɪsəˈleɪʃən/
- Uzun kelimeler — vurguyu doğru yere koyun: 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/
Türkçe konuşanların zorlandığı sesler:
- Kelime başındaki ünsüz kümesi — araya ünlü eklemeyin: startup /ˈstɑɹtˌʌp/, flexibility /ˌflɛksɪˈbɪlɪti/, drawback /ˈdɹɔˌbæk/, scalable /ˈskeɪ.lə.bl̩/, schema /ˈskiːmə/
- /æ/ — “e”den daha açık: drawback /ˈdɹɔˌbæk/, manageable /ˈmænəd͡ʒəb(ə)l/, invaluable /ɪnˈvælju(ə)bl̩/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- Normal hızda cümle cümle tekrar edin; ritminiz konuşmacıyla aynı olana kadar her cümleyi yineleyin.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; radius, registry, flexibility gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.