Prática de Shadowing: System Design Was HARD - Until You Knew the Trade-Offs - Aprenda a falar inglês com vídeo
Escolha um modo de prática
Cada modo abre uma sala de prática em tela cheia.
53 frases
Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.
1
System design is all about making the right trade-offs, whether building something from scratch or scaling an existing application.
2
Understanding these core trade-offs will help us make better architectural decisions.
3
Let's explore some essential system design trade-offs related to data management that every engineer should understand.
4
When it comes to data storage, SQL and NoSQL databases represent fundamentally different approaches with clear trade-offs.
5
SQL databases provide strong consistency, structure schemas, and powerful query capabilities.
6
This structure ensures data integrity, but it creates challenges for horizontal scaling and when modifying schemas.
7
NoSQL databases invert these priorities.
8
They often sacrifice some consistency and query capabilities to gain horizontal scalability and and schema flexibility.
9
With SQL, we're trading scalability for consistency and structure.
10
With NoSQL, we're trading consistency guarantees and query capability for scalability and flexibility.
11
This isn't simply about which is better.
12
It's about understanding the application's specific needs.
13
Do we need rock solid transactions and complex query capabilities?
14
SQL might be the answer.
15
Need to scale massively with evolving data models, NoSQL could be the better choice.
16
Database design typically starts with normalization,
17
organizing data into separate tables to minimize redundancy and ensure each piece of information is stored in only one place.
18
This creates a clean model that maintains data integrity.
19
But as application scale and performance becomes critical, the cost of joins between normalized tables can become prohibitive.
20
This is when denormalization enters the picture, deliberately duplicating data across tables to eliminate expensive joins and speed up common queries.
21
The trade-off is clear.
22
Normalization optimizes for data integrity and storage efficiency,
23
while denormalization optimizes for read performance at the cost of increased complexity in write operations and potential inconsistencies.
24
Most large-scale systems evolve from fully normalized designs towards strategic denormalization only where query performance demands it.
25
This evolution reflects the shifting priorities as applications mature, from correctness and simplicity to performance and scale.
26
In distributed systems, the CAP theorem tells us we can't have it all.
27
Consistency is the assurance of getting the most recent data every single time we make a request.
28
Availability is about ensuring that the system is always up and running, even if some parts are having problems.
29
When network partitions occur, we have to choose one over the other.
30
Banking systems may favor consistency to ensure account balances are always accurate, while social media platforms may favor availability,
31
so users can always access the service.
32
This fundamental trade-off shapes how a system behaves under failure conditions and determines which guarantees we can provide to users.
33
But consistency itself isn't binary, it's a spectrum.
34
Strong consistency is when data updates are immediately reflected across all nodes in the system.
35
It requires synchronization, which can affect performance.
36
Eventual consistency is when data updates a delay before being available across nodes.
37
This approach is faster and more scalable, but users might temporarily see stale data.
38
The tradeoff is between speed and scale versus the immediacy and accuracy of updates.
39
The business requirements dictate where on this spectrum a system should operate.
40
The way we process data presents another fundamental tradeoff.
41
Batch processing accumulates data and processes it at scheduled intervals.
42
This offers computational efficiency and simpler error handling, but introduces significant latency.
43
Users wait hours for insights.
44
Stream processing handles data in real-time as it arrives, providing immediate results and enabling instant reactions to events.
45
However, this introduces complexity because out-of-order data arrivals and variable latency can compromise correctness,
46
requiring sophisticated state management and processing guarantees.
47
The core trade-off is between efficiency and simplicity versus immediacy and responsiveness.
48
Many modern systems end up with hybrid architectures, using streams for time-sensitive processing and batch for comprehensive analysis.
49
Understanding these trade-offs is essential for designing systems that meet our specific requirements.
50
There are no universally correct choices, only trade-offs that align better with a particular use case.
51
If you like our videos, you might like our system design newsletter as well.
52
It covers topics and trends in large-scale system design, trusted by 1 million readers.
53
Subscribe at blog.buybygo.com.
Baixar aplicativo
Tudo o que você precisa para falar fluentemente
Pronúncia com IANota em cada frase
Prática de IPADomine cada som
VocabulárioMonte seu banco de palavras
Jogo de vocabulárioAprenda brincando
Mesmo canal
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
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
C18
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C16
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C13
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity 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
C150
Kubernetes Explained in 6 Minutes | k8s Architecture
Business EnglishUniversity 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
Vídeo recomendado
C12
279 frases
Microservices with Databases can be challenging...
Daily ConversationUniversity StudentsWorking Adults
![The Paradox of Choice • Level 4 [B2] • ESL Listening](https://img.youtube.com/vi/4MzrgdfIgi8/mqdefault.jpg)
B28
14 frases
The Paradox of Choice • Level 4 [B2] • ESL Listening
Daily ConversationUniversity StudentsWorking Adults
C11
52 frases
How to Avoid Doing UX Theatre
Daily ConversationUniversity StudentsWorking Adults
C12
43 frases
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Daily ConversationUniversity StudentsWorking Adults
C11
689 frases
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C13
68 frases
what is a database index?
Daily ConversationUniversity StudentsWorking Adults
C11
274 frases
A 4-Step System to Process Information with Extreme Clarity
Daily ConversationUniversity StudentsWorking Adults
C11
114 frases
Design a File Upload Service Like a Senior Engineer
Daily ConversationUniversity StudentsWorking Adults
C11
180 frases
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C11
275 frases
Every Networking Concept Explained In 20 Minutes
Daily ConversationUniversity StudentsWorking Adults
Vocabulário e dicas de fala para esta lição
Esta aula de conversação de nível C1 usa o vídeo “System Design Was HARD - Until You Knew the Trade-Offs”. As palavras que mais se repetem: consistency, trade, scale, design, query. Este vídeo tem 53 frases e 685 palavras para praticar shadowing. A fala dura 5:06. O falante mantém um ritmo estável de cerca de 134 palavras por minuto, confortável para o shadowing. Apenas 70% das palavras estão entre as 3.000 mais comuns do inglês, por isso o vocabulário é exigente.
Vocabulário principal deste vídeo
As 15 palavras mais avançadas do vídeo, com pronúncia e significado:
| Palavra | Pronúncia | Significado |
|---|---|---|
| consistency substantivo | /kənˈsɪs.tən.si/ | consistência |
| query substantivo | /ˈkwɪɹ.i/ | pergunta |
| capability substantivo | /ˌkeɪ.pəˈbɪl.ɪ.ti/ | capacidade |
| scalability substantivo | /ˌskeɪ.ləˈbɪl.ɪ.ti/ | escalabilidade |
| immediacy substantivo | /ɪˈmiːdi.əsi/ | imediatismo |
| latency substantivo | /ˈleɪ.tən.si/ | latência |
| normalization substantivo | /ˌnɔɹ.mə.ləˈzeɪ.ʃən/ | normalização, normatização |
| normalize verbo | /ˈnɔː.mə.laɪz/ | normalizar |
| optimize verbo | /ˈɑptɪmaɪz/ | otimizar |
| simplicity substantivo | /sɪmˈplɪsɪti/ | simplicidade |
| evolve verbo | /ɪˈvɑlv/ | desenvolver, elaborar |
| horizontal adjetivo | /ˌhoɹəˈzɑn.təl/ | horizontal |
| batch substantivo | /bæt͡ʃ/ | fornada |
| flexibility substantivo | /ˌflɛksɪˈbɪlɪti/ | flexibilidade |
| complexity substantivo | /kəmˈplɛk.sɪ.ti/ | complexidade |
Gramática neste vídeo
As estruturas que o falante mais usa, com as palavras exatas do vídeo:
| Estrutura | No vídeo |
|---|---|
| Voz passiva be + particípio passado — o foco está no que acontece, não em quem faz | is stored · are immediately reflected |
| Orações relativas who / which + oração — informação extra sobre uma pessoa ou coisa | about which is · synchronization, which can |
Pronúncia para ficar de olho
O falante usa 5 contrações e formas reduzidas, como isn't, we're, can't. Diga-as na forma curta, do jeito que você ouve.
- Os sons de “sh” e “zh”: normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/, computational /ˌkɑmpjʊˈteɪʃənəl/, partition /pɑɹˈtɪ.ʃən/, assurance /əˈʃʊɹəns/
- Palavras longas — acerte a sílaba tônica: consistency /kənˈsɪs.tən.si/, capability /ˌkeɪ.pəˈbɪl.ɪ.ti/, scalability /ˌskeɪ.ləˈbɪl.ɪ.ti/, immediacy /ɪˈmiːdi.əsi/, normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/
Sons difíceis para falantes de português:
- Consoante final — sem acrescentar um “i” depois: node /noʊd/, accumulate /əˈkjuːmjʊˌleɪt/, invert /ɪnˈvɜɹt/, dictate /ˈdɪkˌteɪt/, duplicate /ˈd(j)uː.plɪˌkeɪt/
- /l/ final — a língua toca o céu da boca, não vira “u”: horizontal /ˌhoɹəˈzɑn.təl/, computational /ˌkɑmpjʊˈteɪʃənəl/, eventual /ɪˈvɛn.t͡ʃu.əl/, interval /ˈɪntɚvəl/, architectural /ˌɑɹkɪˈtɛkt͡ʃəɹəl/
- /h/ — um sopro suave, diferente do “r”: horizontal /ˌhoɹəˈzɑn.təl/, prohibitive /pɹəˈhɪbɪtɪv/, behave /bɪˈheɪv/
Como praticar com este vídeo
- Ouça o vídeo inteiro uma vez sem falar e anote as palavras que você não conhece.
- Faça shadowing frase por frase na velocidade normal, repetindo cada uma até o seu ritmo ficar igual ao do falante.
- Grave a sua voz e compare com o original, prestando atenção a palavras como consistency, query, capability.
O que é a Técnica de Shadowing?
Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.