Pratique du Shadowing: System Design Was HARD - Until You Knew the Trade-Offs - 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.

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

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

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
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
8 Most Important System Design Concepts You Should KnowC1
8

8 Most Important System Design Concepts You Should Know

Daily ConversationUniversity StudentsWorking Adults
System Design: Why is Kafka fast?C1
1

System Design: Why is Kafka fast?

Business EnglishUniversity StudentsWorking Adults
What Are Microservices Really All About? (And When Not To Use It)C1
6

What Are Microservices Really All About? (And When Not To Use It)

Business EnglishUniversity StudentsWorking Adults
How Does a URL Shortener Work?C1
3

How Does a URL Shortener Work?

Business EnglishInterview EnglishUniversity Students
System Design: Why is Kafka Popular?C1
3

System Design: Why is Kafka Popular?

Business EnglishUniversity StudentsWorking Adults
The Secret Sauce Behind NoSQL: LSM TreeC1
1

The Secret Sauce Behind NoSQL: LSM Tree

Daily ConversationUniversity 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
Kubernetes Explained in 6 Minutes | k8s ArchitectureC1
50

Kubernetes Explained in 6 Minutes | k8s Architecture

Business EnglishUniversity 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 Git Works: Explained in 4 MinutesB2

How Git Works: Explained in 4 Minutes

Business EnglishUniversity StudentsWorking Adults
FOR YOU

Vidéo recommandée

Microservices with Databases can be challenging...C1
2
279 phrases

Microservices with Databases can be challenging...

Daily ConversationUniversity StudentsWorking Adults
The Paradox of Choice • Level 4 [B2] • ESL ListeningB2
8
14 phrases

The Paradox of Choice • Level 4 [B2] • ESL Listening

Daily ConversationUniversity StudentsWorking Adults
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life CycleC1
2
43 phrases

SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle

Daily ConversationUniversity StudentsWorking Adults
Database Sharding! Designing Data-Intensive Applications chapter 6C1
1
689 phrases

Database Sharding! Designing Data-Intensive Applications chapter 6

Daily ConversationUniversity StudentsWorking Adults
what is a database index?C1
3
68 phrases

what is a database index?

Daily ConversationUniversity StudentsWorking Adults
A 4-Step System to Process Information with Extreme ClarityC1
1
274 phrases

A 4-Step System to Process Information with Extreme Clarity

Daily ConversationUniversity StudentsWorking Adults
Design a File Upload Service Like a Senior EngineerC1
1
114 phrases

Design a File Upload Service Like a Senior Engineer

Daily ConversationUniversity StudentsWorking Adults
Armchair Architects: Resiliency in the Cloud – Core PatternsC1
1
180 phrases

Armchair Architects: Resiliency in the Cloud – Core Patterns

Daily ConversationUniversity StudentsWorking Adults
Every Networking Concept Explained In 20 MinutesC1
1
275 phrases

Every Networking Concept Explained In 20 Minutes

Daily ConversationUniversity StudentsWorking Adults
If you’re an aspiring product designer, watch this (roadmap included)C1
5
90 phrases

If you’re an aspiring product designer, watch this (roadmap included)

Daily ConversationUniversity 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 « System Design Was HARD - Until You Knew the Trade-Offs ». Les mots qui reviennent le plus souvent : consistency, trade, scale, design, query. Cette vidéo contient 53 phrases et 685 mots à répéter en shadowing. La partie parlée dure 5:06. Le locuteur parle à un rythme régulier d’environ 134 mots par minute, confortable pour le shadowing. Seuls 70 % 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
query nom/ˈkwɪɹ.i/question
capability nom/ˌkeɪ.pəˈbɪl.ɪ.ti/capacité
denormalization nomdénormalisation
scalability nom/ˌskeɪ.ləˈbɪl.ɪ.ti/extensibilité
schema nom/ˈskiːmə/schéma
correctness nomexactitude, justesse
immediacy nom/ɪˈmiːdi.əsi/immédiateté
latency nom/ˈleɪ.tən.si/latence
normalization nom/ˌnɔɹ.mə.ləˈzeɪ.ʃən/normalisation
normalize verbe/ˈnɔː.mə.laɪz/normaliser
optimize verbe/ˈɑptɪmaɪz/agir en optimiste
simplicity nom/sɪmˈplɪsɪti/simplicité
evolve verbe/ɪˈvɑlv/élaborer
horizontal adjectif/ˌhoɹəˈzɑn.təl/horizontal
batch nom/bæt͡ʃ/fournée

Les verbes à particule que vous entendrez

MotPrononciationSens
speed up verbe/spiːdˈʌp/accélérer

La grammaire de cette vidéo

Les structures que le locuteur utilise le plus, avec les mots exacts de la vidéo :

StructureDans la vidéo
Voix passive be + participe passé — l’accent est mis sur ce qui arrive, pas sur qui le faitis stored · are immediately reflected
Propositions relatives who / which + proposition — une précision sur une personne ou une choseabout which is · synchronization, which can

Prononciation à surveiller

Le locuteur utilise 5 contractions et formes réduites, comme isn't, we're, can't. Prononcez-les sous leur forme courte, telles que vous les entendez.

  • Les sons « sh » et « zh »: normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/, computational /ˌkɑmpjʊˈteɪʃənəl/, partition /pɑɹˈtɪ.ʃən/, assurance /əˈʃʊɹəns/
  • Mots longs — placez bien l’accent: 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/

Les sons difficiles pour les francophones :

  • /h/ — il se souffle, il n’est pas muet: horizontal /ˌhoɹəˈzɑn.təl/, prohibitive /pɹəˈhɪbɪtɪv/, behave /bɪˈheɪv/
  • /tʃ/ et /dʒ/ — à ne pas adoucir en « ch » et « j »: batch /bæt͡ʃ/, eventual /ɪˈvɛn.t͡ʃu.əl/, architectural /ˌɑɹkɪˈtɛkt͡ʃəɹəl/
  • /r/ anglais — langue recourbée, sans frotter la gorge: query /ˈkwɪɹ.i/, normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/, horizontal /ˌhoɹəˈzɑn.təl/, invert /ɪnˈvɜɹt/, prohibitive /pɹəˈhɪbɪtɪv/

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 query, capability, denormalization.

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 →