Shadowing Practice: System Design - Part 1 | Introduction & Career Path | Why you need to learn System Design? - Learn English Speaking with Video

Elige un modo de práctica

Cada modo abre una sala de práctica a pantalla completa.

227 oraciones

Si las oraciones son demasiado cortas o largas, haz clic en Editar para ajustarlas.

It has been quite some time since I have wanted to start my series on system design.

It is just that I never felt ready

that I have all the resources and I have talked about all of the things

that you might encounter while studying this concept.

But right now I feel that I have covered enough that I can begin to talk about system design in general.

And whenever there is a concept that needs more detailing, I will create a video on it.

So with this series, my target is that I want to present your system design in such a way

that you are able to link it correctly to real life problems.

Because I truly believe that if you are able to relate a problem with some real life examples, then it comes very naturally to you.

And that has always been the goal of my channel to simplify the process

and the concept in such a way that it sticks in your mind.

You don't have to just mug up every concept.

So that is exactly what I'm going to do.

Before even getting into, okay, this is system design and these are all the terminology involved, I first want to get into where do you actually encounter system design?

And what are some real -life scenarios where you can apply them?

And that begins with the most basic step.

Where does it come in your interview?

And why do you even need it?

So I believe that will be a good starting point and all along the journey we are going to learn together.

So let's get started over there.

Hello friends, welcome back to my channel.

First of all, when you talk about system design and where does it come in your interview process?

Technically, whenever you are applying at an organization or no matter wherever you are working,

I would broadly say that you are either in the beginner level or you are an intermediate or you are an expert.

That means you have every knowledge or you are a subject matter expert.

So for most of the scenarios, you are at the beginner level.

That means you are dealing with basic data structures, you are dealing with basic algorithms and mostly problems on just to simplify arrays, strings, trees, all of that.

Next comes the part when you are going at a senior level.

So this is where I would say you are going at an intermediate level.

and this is the point where you must have a knowledge of all the system design concepts

because think about it such a large organization like any of the fan companies you know

that you cannot just develop applications based upon all of the data structures

that you have studied right you will not be actually using an array and then making all of these huge applications Correct?

You need a very good architecture level diagram and then you want to deploy out all the several components.

Correct?

Now, when you are at a beginner level, it is not expected out of you that you make these design decisions.

What usually happens is, at the beginner level, you are just given a sub -module that, hey, this is an entire application and you have to solve this small bit.

And that is why interviewers focus more on your data structures and problem -solving abilities.

when you are applying for intermediate roles that is where you want to know

that you have a knowledge of all of the design level concepts as well

because how is a system working what is actually happening what's

the database what is caching how is the data flowing what requirements do you want

so this is where you will start to get all of these questions and for example you're applying at Google.

So Google explicitly asks you, hey, do you want a system design coding round in your interview process or not?

And for other companies like Amazon, they will add a system design round if you're applying to software engineering levels of two and above.

So that is the idea.

And when you get at an expert level, you are not asked about data structures, algorithms.

No, that doesn't happen.

What happens is then you have to talk about real life applications.

How would you deal with this bunch of customers?

How would you deal with the high traffic?

How would you scale the application all throughout?

So, I know that all of these are very high -level terms, and surely we will get into the details of all of it.

But you must understand that where does system design come into play, and it is this particular level.

So, if you want to grow in your career, and if you want to reach at an expert level, that is where you need to have this knowledge.

Because, although you have these three levels, but the pay grade, it increases exponentially as you move towards the expert level.

And everybody loves a good pay, correct?

So, that is why system design is very, very necessary.

You want to know, right?

How is Netflix working?

How is YouTube working?

How are you handling so many customers?

Think about it.

Netflix is available all throughout the world.

And on YouTube, you can live stream a YouTube video even with millions of viewers.

So how are you handling all of that traffic?

That is all behind what system design is.

How are you designing this entire application?

So that is the end goal.

But before that, we want to understand what the hell is even system design and why do you want to scale applications?

Or rather, what does scaling even mean?

I will start from the very basic and then we will go along building our way step by step.

So where do you start?

Well, why do you even need system design?

And to understand it, let us go to the ground level.

Forget everything about computers.

Just focus that, let us say you want to open a bookstore, right?

And what do you do?

Okay, you have a small bookstore you open it what happens now you can say

that okay some customers will start to come in now as more

and more customers start to come in what do you do your bookstore will start to get smaller right

so you want to accommodate more customers what is the first thing

that comes to mind okay this is a small shop what

do i do i will try to either expand my shop

or what i'm gonna do is i will shut down this store

and maybe i open an even bigger store correct now you have a bigger store

and what happens is you see more

and more customers come in your store is able to accommodate everyone

so what are you basically doing you are increasing your store capacity correct

and this process cannot just go on think about it what

if more customers starts to come in you have a lot of customers coming in correct

so what do you do now Okay, maybe I can increase my store once again.

My bookstore is even bigger now and I can accommodate more people.

But do you see the problem with this approach?

What if more and more customers start to come in?

What if you're becoming really, really popular?

Do you think that you can keep on expanding a bookstore?

You will face all of the issues, right?

You cannot have a very huge building.

100

You will have all these parking problems and all of the resources problems as well.

101

You cannot manage all the customers.

102

It will be all of a hassle, right?

103

So basically what you're currently doing right now is you are scaling your bookstore vertically.

104

That means you are gonna keep on increasing the size of your bookstore.

105

You will soon realize that you are running out of space, correct?

106

So you already know what solutions do all of these big companies come up with right

107

and what is

108

that they do not open a store at only one place

109

what will you do you will open different stores at different places correct

110

and each of these stores they are made on the basis

111

of your consumption correct you do not want to open a huge store where the footfall is very less

112

and vice versa

113

so basically what are you doing you are trying to expand

114

your business horizontally what you can do is you can use your same store format

115

and open it up in a lot of different places what did

116

that do with this you can distribute all of your customers at different places correct think about it

117

if you had your store open only in one region then

118

you're only targeting customers from this particular region you cannot expect

119

that someone will fly all the way to come at your store.

120

But if you have opened your store at all of these different places, a customer can go to any of the store that is nearest to them.

121

So this is how you are solving a problem.

122

And this is horizontal scaling.

123

So now you are understanding the two most important concepts, vertical scaling and horizontal scaling.

124

You cannot expect to have vertical scaling infinitely but with horizontal scaling you have a lot more scope.

125

So this was a pretty basic example when you were trying to open a bookstore and then you want to expand it.

126

You want more profits right and when it comes to computer programming

127

or making applications what happens is let us say you are developing an application correct

128

and this application will be having a database it will have some disk usage

129

and it will have some cpu as well

130

and now think about it you made your application on a

131

computer correct very basic let us say you have your home computer

132

and you made an application on it now let's say you

133

want to make this application available to someone you run your own server

134

and then you deploy this application so people will start coming in

135

and they will want to use your application correct but

136

if you notice the more

137

and more people will try to use your app what will

138

happen you will need more disk you will need more cpu and you will need more database as well So, the same concept applies over here.

139

Yes, you can increase your disk size and then you can even use a faster CPU.

140

Right now, you are having a 2 .2 GHz CPU.

141

You can switch to a 3 GHz.

142

Similarly, for a disk, you can have 2 TB of RAM and then you can upgrade to 4 TB of RAM.

143

Similarly, for database as well.

144

But do you see the problem?

145

If you have to deal with millions of users, think about Facebook, right?

146

You have so many users you cannot expect that you will keep on increasing your disk, database and CPU quantity.

147

You are limited, right?

148

You do not have a faster CPU than a particular limit, correct?

149

Another factor is that when you are dealing with such large memories, then the cost of things also start to grow.

150

I am pretty sure that when you have purchased components, you might have seen this as well.

151

For example, if you are taking two RAMs of 4TB each, they will cost you less than a single piece of 8TB RAM.

152

So, the price required is not linear.

153

So, you cannot keep on increasing your RAM continuously.

154

Your cost will keep on increasing exponentially and you will never make a profit.

155

In fact, if you look at the graph between your cost and memory, this graph will look something like this.

156

So as you increase your memory, the cost keeps on going up, right?

157

And whenever you're dealing with applications, you need more RAM, more and more fast memory.

158

So at that point, your application stops scaling.

159

You cannot just accommodate more and more customers to reach you.

160

So this is exactly similar when you're opening a bookstore, correct?

161

You cannot just keep on increasing your bookstore size.

162

You will face some of the problems.

163

And when you're dealing with computer applications, you get limited by all of these resources.

164

To give you an example, I just took two screenshots.

165

Just look at this.

166

Here is a solid state drive and for 4TB, the cost is approximately $230.

167

So, you would expect that, okay, for 8TB, I will get the double of cost, right?

168

But that is not true for high memories.

169

If you are increasing your storage size then the cost becomes greater than a multiple of two

170

and that is why you cannot just keep on having a vertical scaling.

171

You need to think something different and that is where horizontal scaling comes in.

172

Similar to the way we were opening all of our bookstores

173

what we now do is we take up our app

174

and we will try to deploy it in two different regions of the world.

175

So now what happens?

176

All of your customers that were coming from all the way to the world only in one region.

177

This was our condition, right?

178

And this was causing a problem.

179

What did we just do?

180

We have now deployed our applications in two different regions.

181

And now some customers can reach over here while the other users can reach over here.

182

So what did you do?

183

You partitioned your users, correct?

184

And you are able to give them the same service.

185

So this is a very high level overview design about what is a vertical scaling and what is a horizontal scaling.

186

And this is the exact reason why you need to study system design.

187

Because you cannot just keep on scaling up your application vertically.

188

It is just not possible you need to have different servers all throughout the world.

189

That is why you have so many services in all different regions of the world.

190

That is why there is a concept of latency because it depends which server are you trying to connect to.

191

If a server is hosted only in the Americas then this is the latency from all different countries.

192

So these are all the concepts that we will become familiar with

193

but for this video i just want to give you an overview

194

that this is system design and that is why we study it

195

and i really hope that this kind of peaks your interest

196

and you want to know more

197

and this is how i'm gonna structure my course as well

198

so basically what we are gonna do is just like this

199

real life example we will cover all of the basics of system design that means what are all the terminology used?

200

What is caching?

201

What is latency?

202

What is partitioning?

203

What is hashing?

204

What do all of these actually mean?

205

And we will go step by step over every example.

206

What is the individual component doing and how can you take advantage of it?

207

And once you are familiar with all of these basic concepts, we will start off with some very basic designs.

208

For example, how do you implement a service that is a URL shortener?

209

How do you implement a service something like Uber?

210

So just a basic idea, like how do you have this map structure and how do you find the nearest cab?

211

So these are some of the very basic designs and then we are going to understand each of the components as well.

212

So what I want to just say is, it is a journey and it will take some time.

213

Just keep letting me know if you are facing any problems and which part do you want me to expand more.

214

Just tell me if it gets very verbose or

215

if it starts to get boring

216

but all of this feedback will help me to curate this course even more effectively

217

and I promise I will try to simplify it as much as possible for you

218

and if everything goes right we will also look at some complex designs and some real -life applications too.

219

So that is all I had in my mind for now

220

so do let me know what are you feeling about this course

221

and are you looking forward to it that will surely keep me motivated.

222

Also if you find this channel helpful

223

and you really like these kind of explanations please do subscribe to my channel it really keeps me going

224

and if you want more consider joining my channel by

225

that you do get prior to reply to your comments

226

and you do get early access to these new videos as well

227

so stay tuned for my upcoming videos until then see ya

Descargar app

Todo lo que necesitas para hablar con fluidez

Pronunciación con IAEvalúa cada oración

Práctica de IPADomina cada sonido

VocabularioConstruye tu banco de palabras

Juego de vocabularioAprende mientras juegas

Escanea el QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Recomendar Video

99 oraciones

What are Design Patterns? | Introduction to Design Patterns and Principles | Geekific

Business EnglishUniversity StudentsWorking Adults

227 oraciones

Civil 3D course for beginners - Part 1 of 3

Business EnglishUniversity StudentsWorking Adults

264 oraciones

System Design Mock Interview: Design WhatsApp

Business EnglishInterview EnglishUniversity Students

263 oraciones

Anthropic's CCA Exam as a Field-Guide for Agentic Engineering — Frank Coyle, UC Berkeley

Business EnglishInterview EnglishUniversity Students

275 oraciones

How to Prepare for System Design Interviews w/ Meta Staff Engineer

Interview EnglishUniversity StudentsWorking Adults

Vocabulario y notas de pronunciación para esta lección

Esta lección de conversación de nivel C1 se basa en el vídeo “System Design - Part 1”. Las palabras que más se repiten: design, application, customer, correct, store. Este vídeo tiene 227 frases y 2833 palabras para practicar shadowing. La parte hablada dura 16:04. El hablante habla a un ritmo natural de unas 176 palabras por minuto, cercano a una conversación cotidiana. El 89 % de las palabras está entre las 3.000 más comunes del inglés; conviene repasar el resto antes de empezar. 53 de sus 227 frases son preguntas, así que sirve para practicar la entonación de las preguntas y las respuestas cortas.

Vocabulario clave de este vídeo

Las 15 palabras más avanzadas del vídeo, con su pronunciación y significado:

Palabra	Pronunciación	Significado
horizontal adjetivo	/ˌhoɹəˈzɑn.təl/	horizontal
disk sustantivo	/dɪsk/	disco
beginner sustantivo	/bəˈɡɪnɚ/	bisoño, novato
deploy verbo	/dɪˈplɔɪ/	desplegar
accommodate verbo	/əˈkɑməˌdeɪt/	acomodar
latency sustantivo	/ˈleɪ.tən.si/	latencia
simplify verbo	/ˈsɪmplɪfaɪ/	simplificar
intermediate adjetivo	/ɪn.tə(ɹ)ˈmi.di.ət/	intermedio
exponentially adverbio	/ɛkspə(ʊ)ˈnɛnʃəli/	exponencialmente
vertically adverbio	/ˈvɝ.tɪ.kəli/	verticalmente
cache sustantivo	/kæʃ/	memoria caché, caché
partition sustantivo	/pɑɹˈtɪ.ʃən/	parte
terminology sustantivo	/ˌtɝ.məˈnɑ.lə.d͡ʒi/	terminología
algorithm sustantivo	/ˈælɡəɹɪðm̩/	algoritmo
graph sustantivo	/ɡɹæf/	gráfico, gráfica

Phrasal verbs que vas a escuchar

Palabra	Significado
come up with verbo	ingeniar, ingeniarse
go up verbo	subir
look forward to verbo	no ver la hora de, quedar a la espera de
shut down verbo	apagar
start over verbo	volver a empezar, empezar de cero
step over sustantivo	bicicleta

Frases que vale la pena repetir

Frases cortas y completas del vídeo que puedes reutilizar en la conversación diaria:

Where does it come in your interview?
How would you deal with this bunch of customers?
How would you deal with the high traffic?
How would you scale the application all throughout?
What if you're becoming really, really popular?

Gramática en este vídeo

Las estructuras que más usa el hablante, con las palabras exactas del vídeo:

Estructura	En el vídeo
Present perfect have/has + participio pasado — una acción pasada que sigue importando ahora	has been · have talked · have covered
Voz pasiva be + participio pasado — importa lo que ocurre, no quién lo hace	is not expected · are just given · are not asked

Pronunciación a tener en cuenta

El hablante usa 17 contracciones y formas reducidas, como you're, gonna, I'm. Dilas en su forma corta, tal como las oyes.

Los sonidos de “sh” y “zh”: exponentially /ɛkspə(ʊ)ˈnɛnʃəli/, cache /kæʃ/, partition /pɑɹˈtɪ.ʃən/, shortener /ˈʃɔɹtənɚ/, hash /ˈhæʃ/
Palabras largas — cuida el acento: horizontal /ˌhoɹəˈzɑn.təl/, accommodate /əˈkɑməˌdeɪt/, intermediate /ɪn.tə(ɹ)ˈmi.di.ət/, exponentially /ɛkspə(ʊ)ˈnɛnʃəli/, vertically /ˈvɝ.tɪ.kəli/

Sonidos difíciles para hispanohablantes:

/v/ — no es /b/: los dientes tocan el labio inferior: vertically /ˈvɝ.tɪ.kəli/, verbose /vəˈbəʊs/, interviewer /ˈɪntɚvjuɚ/, motivate /ˈmoʊ.tɪ.veɪt/, viewer /ˈvju.ɚ/
/dʒ/ — no es la “y” ni la “ch”: terminology /ˌtɝ.məˈnɑ.lə.d͡ʒi/, module /ˈmɑd͡ʒul/
/h/ — una aspiración suave, no la “j”: horizontal /ˌhoɹəˈzɑn.təl/, hassle /ˈhæsl̩/, hash /ˈhæʃ/

Cómo practicar con este vídeo

Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
Empieza a velocidad 0,75×, haz shadowing frase por frase y vuelve a la velocidad normal cuando te resulte fácil.
Grábate y compara con el original, prestando atención a palabras como horizontal, disk, beginner.

¿Qué es la Técnica de Shadowing?

Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.

Técnica de shadowing: lee la guía completa paso a paso →

Shadowing Practice: System Design - Part 1 | Introduction & Career Path | Why you need to learn System Design? - Learn English Speaking with Video

Elige un modo de práctica

Descargar app

How to Answer System Design Interview Questions (Complete Guide)

Meet New People! Self Introduction in English: Business English at Work

Data Structures Explained for Beginners - How I Wish I was Taught

Incident Management Process: A Step by Step guide

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

My Senior UX Design Interview Experience | tips, questions, prep, & more!