Shadowing Practice: How Uber Scaled from One Server to 150 Million Reads Per Second - Learn English Speaking with Video
Kies een oefenmodus
Elke modus opent een volledig scherm oefenruimte.
134 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
In 2009, Uber was starting with a Python mullet.
2
One application, one growing business.
3
By 2019, Uber reported more than 15 million trips a day.
4
And in 2025, its caching infrastructure reported over 150 million cache database row reads per second at peak.
5
So how does a system grow at that scale?
6
Let's build it step by step.
7
Imagine you are building Uber you start with one application
8
and a postgres database and this is called monolith
9
and all your main application features live inside one application
10
and early days that's not a bad thing it's easier to build test
11
and deploy code but now more rides are booing trips more drivers are sending updates
12
and your application has work to do if the application and database share one machine they compete for the CPU and RAM.
13
The database run queries, the application handle request and both need resources.
14
One solution is to move the database onto its own server.
15
Now the application and database have separate resources.
16
You can scale them independently but there is a catch.
17
They now communicate over a network and the database can still become a bottleneck.
18
Meanwhile your application is also getting more traffic.
19
So let's scale your application first the simplest option is to give your application server more cpu
20
and memory and this is called vertical scaling it can work well
21
when you are just starting out you don't need to redesign everything just
22
because traffic increases but one machine has limits and
23
if it fails your application may become unavailable
24
so instead of making one server bigger you can add more servers
25
and that is horizontal scaling now you have multiple servers handling request
26
but there's a new question when the request arrives
27
which server should handle it
28
so you put a load of answer in front of replication server
29
it distributes incoming requests across them it can use strategies like round robin
30
or lease connection
31
and health checks can help it avoid sending traffic to unhealthy server
32
now one server failing does not necessarily take down the whole application
33
but there is a other problem imagine a user logs in replication store their session on the first server
34
then the user's next request reaches a different server
35
that server may not have the session so how does it know
36
that you are logged in one option is to store session in a shared system such as redis
37
now any application server can retrieve the session
38
and other option is to use a token such as gwd
39
that carries signed claims that can reduce the need to look up a session on every request.
40
But remember, tokens don't eliminate every kind of server -side state.
41
The key idea is simple.
42
Don't make one application server the only place where information needed by the next request exists.
43
We've added application servers, but all of them still depend on database.
44
And every request does not necessarily need to read fresh data from it.
45
Some data gets requested repeatedly, and that is where caching comes in.
46
Imagine a request needs a piece of data.
47
First, the application checks the cache.
48
If the data is there, it returns it and that is cache hit.
49
If it is missing, the application fetches it from database
50
and can put it in the cache and that is a cache miss.
51
The next request may get the data without querying the database again.
52
But caching introduces a problem.
53
What happens when the original data changes?
54
The cached copy might become stale.
55
You can use techniques such as time to live or TTL to expire entries.
56
You can also use invalid cache data when the underlying data changes.
57
Strategies like write -through or write -around handle writes differently.
58
And there is no single strategy that's best for every workload.
59
Uber has built caching infrastructure called CacheFront.
60
In August 1995, Uber reported that it handled more than 150 million cache row reads per second at peak.
61
Notice what that number means.
62
It's cache database row reads handled by that infrastructure.
63
And it does not mean every database read across
64
Uber was subbed from the cache.
65
Caching can remove a lot of repeated work, but it does not solve every database problem.
66
Some applications read data far more often than updated.
67
For those workloads, you can introduce read replicas.
68
The primary database handle writes, replica receive copies of the data then application can send suitable read queries to those replicas
69
that take some read traffic away from the primary
70
but there is an important catch replication can take time the primary might have the latest update
71
while the replica is still catching up and this is called replication lack
72
so if a request need the fresh data you may need a read from the primary.
73
Replica help with re -capacity but they don't automatically solve right bottlenecks or storage limits.
74
Now imagine your trip data keeps growing.
75
Eventually one database may struggle to store and serve everything efficiently.
76
Uber ran into storage challenges with the Postgres -packed trip data in its early growth period.
77
It developed a system called SchemaLess on top of MySQL.
78
This brings us to another scaling technique.
79
It is called Sharding.
80
Instead of storing all the data on one database, you split it across multiple database groups.
81
For example, imagine dividing trips into groups based on hash of the trip identifier.
82
One group stores some trips, another group stores others.
83
The application needs a way to work out which group contains the requested trip.
84
And that is the basic idea.
85
This example explains sharding.
86
It is not a claim about Uber's exact partitioning algorithm okay
87
so sharding lets you distribute data and workload
88
but now your application need to know where each record live
89
and the workload might not be evenly distributed imagine one shard receiving far more requests than the others
90
that shard can become a bottleneck even when the rest are healthy
91
and this is also called a hot shard so sluting the data helps but it also makes data management more complicated.
92
Okay, so there is one more challenge.
93
As the developer team grow, more developers work on the same application.
94
A change in one area might affect other.
95
Deployment can become much harder to coordinate.
96
One response is to split the application into small services.
97
And Uber documented its move toward a microservice architecture in 2015.
98
So imagine this.
99
Payments, pricing, and trips matching as separate services.
100
These are illustrative examples of how an application can be divided.
101
Each service can have its own code base and deployment process.
102
Teams can work more independently, but now one user request might depend on several services working together.
103
And that creates a different kind of problem.
104
Okay, inside one application, calling a function is usually straightforward.
105
For example, a fare calculation function might take the trip details as input and return the calculated fare.
106
But when one service calls another service over a network, things change.
107
The other service might be slow or it might be unavailable or the network request might time out.
108
Now you need to handle failure across service boundaries.
109
Okay, so when an application has many services, finding the cause of slow request gets hard.
110
Was the delay in pricing, was it payments or was one service waiting on another?
111
So Uber developed Yaeger, a distributed tracing system to help engineer follow requests across services.
112
Tracing helps you to see where time is spent and where request is failing.
113
Without that visibility, debugging a distributed system becomes much harder.
114
Ok, as the services multiply, service discovery and communication also becomes more complicated.
115
A service needs to find the service it wants to call.
116
And the system need to handle those connections reliably.
117
So Uber developed Hyperband as a part of its service communication infrastructure.
118
So engineers also used general resilience patterns such as timeouts, retries and circuit breakers.
119
But those patterns need careful configuration.
120
Retries for example can make an overload service even busier.
121
So by July 2020, Uber had described an architecture with around 2200 critical microservices organized into 70 domains.
122
These 70 domains were not 70 services.
123
They were broader grouping used to organize services.
124
And that is important lesson here.
125
Microservices can be more independent but also create more dependence, more network calls, more operational complexity.
126
So just look at the progression.
127
You start with one application, then you separate the database, you add application servers, you share session state, you introduce caching and read applicas,
128
you shard the data, and eventually you split the application into services.
129
Each decision solves a problem, but each decision also introduces a new trade -off.
130
That's how production systems grow.
131
Not by adding every technology from the beginning, but by identifying the bottleneck, choosing a solution, and understanding the new problem that solution create.
132
When you are designing a system, don't just ask, what technology should I use?
133
Ask, what problem am I solving and what trade -off am I accepting?
134
Save this for your next systemline interview and follow for more.
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
FOR YOU
Aanbevolen Video
C18
67 zinnen
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C15
183 zinnen
The Gig Economy is Full
Daily ConversationUniversity StudentsWorking Adults
C11
65 zinnen
Did Anthropic Kill Git?
Daily ConversationUniversity StudentsWorking Adults
C11
498 zinnen
Give me 31 minutes, I will make PyTorch click forever
Daily ConversationUniversity Students
C11
78 zinnen
How I deploy serverless containers for free
Daily ConversationUniversity StudentsWorking Adults
C11
124 zinnen
Agentic AI Frameworks Explained: Workflows, Multi-Agent, & Production
Daily ConversationUniversity StudentsWorking Adults
C11
847 zinnen
The Complete Guide to Hybrid Search in RAG (BM25 + Embeddings + Reranker)
Daily ConversationUniversity Students
C11
623 zinnen
The Only SaaS Moats Left in 2026
Daily ConversationUniversity StudentsWorking Adults
C1231 zinnen
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C11
689 zinnen
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
462 zinnen
Expensive RTX 5090 for LLMs? NO. Use This Instead. (Tesla V100 SXM2 + Z8 G4, #RACERRRZ)
Daily ConversationUniversity StudentsWorking Adults
C11
466 zinnen
DejaVue #E001 - The Need for Server-Side Rendering (SSR)
Daily ConversationUniversity Students
Woordenschat en spreektips bij deze les
Deze spreekles is gebaseerd op de video “How Uber Scaled from One Server to 150 Million Reads Per Second”. Deze woorden komen het vaakst terug: application, database, server, request, Uber. Deze video bevat 134 zinnen en 1507 woorden om na te spreken. Het gesproken deel duurt 9:46. De spreker praat in een natuurlijk tempo van ongeveer 154 woorden per minuut, dicht bij een alledaags gesprek. Slechts 79% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| database zelfstandig naamwoord | /ˈdeɪtəˌbeɪs/ | database, databank |
| server zelfstandig naamwoord | /ˈsɝvɚ/ | server |
| cache zelfstandig naamwoord | /kæʃ/ | cache |
| distribute werkwoord | /dɪˈstɹɪbjuːt/ | verdelen |
| infrastructure zelfstandig naamwoord | /ˈɪnfɹəˌstɹʌkt͡ʃə/ | infrastructuur |
| solve werkwoord | /sɒlv/ | oplossen |
| introduce werkwoord | /ˌɪntɹəˈdus/ | introduceren, voorstellen |
| query zelfstandig naamwoord | /ˈkwɪɹ.i/ | vraag, verzoek |
| necessarily bijwoord | /ˌnɛs.əˈsɛɹ.ə.li/ | nodig, noodzakelijk |
| complicated bijvoeglijk naamwoord | /ˈkɑm.plɪˌkeɪ.tɪd/ | ingewikkeld, gecompliceerd |
| technique zelfstandig naamwoord | /tɛkˈniːk/ | techniek |
| architecture zelfstandig naamwoord | /ˈɑː.kɪˌtɛk.t͡ʃə/ | architectuur, bouwstijl |
| log zelfstandig naamwoord | /lɔɡ/ | boomstam, boomstronk |
| domain zelfstandig naamwoord | /ˌdəʊˈmeɪ̯n/ | domein |
| depend werkwoord | /dɪˈpɛnd/ | afhangen |
Phrasal verbs die je zult horen
| Woord | Uitspraak | Betekenis |
|---|---|---|
| look up werkwoord | /ˌlʊk ˈʌp/ | opkijken |
| work out werkwoord | /ˌwɝk ˈaʊt/ | uitrekenen |
Grammatica in deze video
De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:
| Structuur | In de video |
|---|---|
| Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet | is called · are logged · was subbed |
| Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telt | We've added · has built |
Uitspraak om op te letten
De spreker gebruikt 6 samentrekkingen en verkorte vormen, zoals don't, we've. Spreek ze kort uit, zoals je ze hoort.
- De “th”-klanken: algorithm /ˈælɡəɹɪðm̩/, unhealthy /ʌnˈhɛl.θi/, monolith /ˈmɑn.əˌlɪθ/
- De klanken “sh” en “zh”: cache /kæʃ/, operational /ˌɑ.pəˈɹeɪ.ʃə.nəl/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, progression /pɹəˈɡɹɛʃən/, calculation /ˌkælkjuˈleɪʃn̩/
- Lange woorden — let op de klemtoon: infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/, complicated /ˈkɑm.plɪˌkeɪ.tɪd/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, developer /dɪˈvɛləpɚ/
Klanken die Nederlandstaligen lastig vinden:
- Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: solve /sɒlv/, complicated /ˈkɑm.plɪˌkeɪ.tɪd/, log /lɔɡ/, depend /dɪˈpɛnd/, divide /dɪˈvaɪd/
- /æ/ — opener dan de Nederlandse “e”: cache /kæʃ/, algorithm /ˈælɡəɹɪðm̩/, calculate /ˈkælkjʊleɪt/, calculation /ˌkælkjuˈleɪʃn̩/, hash /ˈhæʃ/
- /g/ — een harde plofklank, geen Nederlandse “g”: log /lɔɡ/, organize /ˈɔɹɡənaɪz/, algorithm /ˈælɡəɹɪðm̩/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, progression /pɹəˈɡɹɛʃən/
Zo oefen je met deze video
- Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
- Begin op 0,75× snelheid, spreek zin voor zin na en ga terug naar normale snelheid zodra het makkelijk gaat.
- Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als database, server, cache.
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.