The Real Hidden Cost of a Request

preview_player
Показать описание
In this video I explore the hidden costs of sending a request from the frontend to the backend

More details here

Discovering Backend Bottlenecks: Unlocking Peak Performance

Fundamentals of Backend Engineering Design patterns udemy course (link redirects to udemy with coupon)

Fundamentals of Networking for Effective Backends udemy course (link redirects to udemy with coupon)

Fundamentals of Database Engineering udemy course (link redirects to udemy with coupon)

Follow me on Medium

Introduction to NGINX (link redirects to udemy with coupon)

Python on the Backend (link redirects to udemy with coupon)

Become a Member on YouTube

Buy me a coffee if you liked this

Arabic Software Engineering Channel

🔥 Members Only Content


🏭 Backend Engineering Videos in Order

💾 Database Engineering Videos

🎙️Listen to the Backend Engineering Podcast

Gears and tools used on the Channel (affiliates)

🖼️ Slides and Thumbnail Design
Canva


Stay Awesome,
Hussein
Рекомендации по теме
Комментарии
Автор

Head to backend.win to grab my fundementals of backend engineering course

hnasr
Автор

I absolutely love how you get to the bottom of how things work and strive to never forget or omit the low-level details. For some reason it's really uncommon compared to using things without asking any questions. That is what makes going through the education system so frustrating to me, dogmatic thinking. Your channel is one of my favourites because of this spirit of curiosity. Keep up the good stuff <3

supernovaw
Автор

Nice video, while you were explaining it triggered me the thought of how you handle race conditions if the previous request is waiting and then the next request do some changes in db which first checks in db for an early entry by a call to db. But in second request the things have changed and check which was to be made in db is now bypassed by race conditions or fast multiple requests. I hope this makes sense.

megamind
Автор

Really like this. All the abstractions and libraries these days are a double edged sword. Yes you can develop faster, but you are also less aware of what is actually happening computationally.

bellybooma
Автор

Really love how amazingly complex this request is and we ignore this. Amazing show video.

qkohtdg
Автор

Go through the medium article and pen down it somewhere after having a look at this video. Really informative.

srihari
Автор

Great video, I'd love if you dive deeper into how processes is handled and the resources they consume, especially capacity planning

sherifalaa
Автор

I won't lie.
Sometimes it's best to create a websockets request/response type of simple protocol for your needs and do much of the requests through it instead of fetch/ajax.
Way lower latency, no overhead for handshakes, etc. If you're really crazy about it, you can just as well stream images and media like that.

shapelessed
Автор

Good video topic and AWESOME Cow-lick on the hair!

IntenseWebs
Автор

You talk about the costs ... what about the costs for Spring Boot framework ... traditional approach @RestController ... ?

bogdy.musiclover
Автор

It resembles Star Trek's teleportation, as the request de-materialize in one end, travels through space, and re-materialize in other point (address) ... 😊
But, by all means, what is then the real cost of a request (in dolar, per request), approximately ? 🤔

kdcapparelli
Автор

1. Do you have any course to become a good nodejs developer with mongo?
2. Basics of system design

rajashekhar
Автор

I have a problem to solve around something similar, to determine if I have recieved a similar (not same) request based on some parameter / data in the last request for that subject, to decide should I let it through or not (if its a duplicate/something that doesn't add anything new to update on the items my downstream is interested in).
Again this can lead me to race conditions, where by the time I am at the stage of deciding this present request is duplicate, another duplicate comes at the top when I search the stack.

testemail
Автор

Talk about SNMP (Simple Network Management Protocol) please ^^

RealYukiSan
Автор

@hnasr you should do a video covering L4S aka RFC 9330. This is IMHO a gamechanger in the fight against bufferbloat and high latencies.

btom
Автор

Can you explain system design diagrams at least in a conceptual level?
I am an aspiring backend developer, and I find myself building more and more complex (at my level) functions. But each time when I do some basic flow, I find myself doing different implemwntation

leojohn
Автор

I thought you will start from the point where the client start to make the request obj we have also a lot of steps to go through until we get the request to be in the wire

mohammedabdulbary
Автор

Thank you Hussein! one question: out of all the stages, would decryption be the slowest?

kiang.
Автор

Hussein, why do you have 2 copies of Steve Jobs by Walter Isaacson on your bookshelf behind you? Isn't that redundant? I noticed it today while watching the Caching Techniques video of yours from 3 years ago. :D

gibraanjafar
Автор

After 5 minutes of waiting for you to get to the point of this video... I gave up and clicked to another video.

JamieTransNyc