It is very interesting and fun video :). Maybe it would be more precise and fair to compare the time starting from the line we begin our task, this will give the real time that takes the task, as the runtime is usually started only once.

Thanks

In other words, a top-down approach is generally considered more efficient than a bottom-up approach.

love these podcasts

Can we create Api endpoints?? like forward to particular endpoint if it matches /api, /api1

Long polling diagram as i userstood from your video - drive.google.com/file/d/1w5nXI3Evk1WMm1hlm5Xbhr9pP-99kDN7/view?usp=sharing

Allahu Akbar now 444k subscriber

I have django project and now I hit multiple requests but its fails its only process one request at a time help me to process multiple requests in django parallel processing

thanks for reading a doc for us

Retard talked nonsense for 28 mins instead of just explaining the concept in like 10 mins. Dumbass

I a mistake in an aws question because poll and pull guessing lol

28:12 Thanks for clarifying, at first I thought we were talking about socket sharting.

Won't Long polling block the threads on backend which will eventually be a disaster for backend as it may have finite number of threads?

i open my router's admin panel to the internet so that it never gets lonely :3

Hussein Please make a microservice course on udemy your teaching style is best in the market.

perfect explanation👌

Was the best , as clear as possible!

Love this, but wouldn’t a push system be better is most of these scenarios? Is the case against websockets is that’s it’s quite resource intensive to keep connections alive, especially for cases where most of these scenarios application doesn’t need the “real timeless”

I'm considering having my requests respond with an "expected ready time" then the client only checks again if its past that, but obviously this doesn't work in all cases.

Won't having open requests (at least in HTTP) consume a lot of memory on the server?

Hi Hussein! For the queue example, using the long polling model, are we essentially shifting the short polling process from the frotend (browser) <-> backend to the backend <-> event queue? If the client polls and the resource isn’t ready yet, the backend doesn’t respond immediately. Instead, it has to keep checking whether the resource has been processed and is available in the queue to be consumed, essentially short polling. Is this the standard way?

what polling strategies can be implemented on the client-side if we do not have control of the BE? Can we do any better than some tailored/configurable exponential-backoff. Lets say we have costly api calls and the service provider only supports a GET/ status request.

I have heard many engineers but very few wiser than this guy.

Hey Hussein, When do we choose Long polling over websockets?

24:15 sure just gloss over the headline. As far as I know the proxy isn't going to tell the server that anything happened. Maybe if the server has a good stack implementation it can catch the event by writing to a bad socket. But that is a big if. This just creates the opportunity for the backend to increment the pointer without verifying that the client was synced. If polling is absolutely required the it would be way saner to cache and not keep long lived connections open for no reason. But polling is almost never required these days.

I'm at 4:55 and I'm about the guess what long polling means. My guess is, why can't we just wait with the response. When there is no result, don't say there's no result, just wait until there is a result and then respond. Then you might only have to poll like every say minute, and it times out every minute, hence the name long polling.

India jio sni plz

the confusion i was having for the last few weeks just vanished away at 5:12 , nobody on this platform ever bothered to mention that this was an old method and the new method incorporates DH key exchange algo. THANK YOU A LOT HUSSEIN !

Would be nice if you share some resources or articles.

But they say texts are encrypted. Is it though

I'm not sure if I caught this, but how does this work in a distributed system? Suppose the Client makes the initial request to Node 1 to generate the report. Then, the same Client makes a long poll request to Node 2 to get the report when it is ready. How is the system set up such that when the report is actually generated, all Nodes receive this event and sends the response to all clients accordingly? Does each node need to have some kind of consumer to consume "completion" events from some centralised queue? Or do workers push this "completion" event (perhaps by some API call) to all nodes once they are done? Also, if too many clients hold a long polled connection to a server, at some point will the server no longer be able to handle any incoming connections?

Git Pull😏

I love it!

443k subs, ur channel is safe now(:

Hussein. I would be interesting to compare HTTP long-polling to Websocket for push updates. I know they are both TCP technologies and one is true duplex and real-time but that comes at a cost. Do you know how expensive is it for say 1 million long-polled connections vs. 1 million Websocket connections both at idle? I would assume long-polling would win in terms of raw resource requirements and compute or am I wrong?

Loved the way of explanation

Please, no deployment to fridges. 😭

Hi Hussein, I just want to confirm that the api on which we get the uuid from the server and the api on which the client asks for the status of that uuid are different apis, right?!

Excellent one! Thanks! Much appreciated.

It's fascinating to watch this, especially since I’ve been researching event-driven protocols, WebSockets, and fallback mechanisms as polling. I wasn’t familiar with long polling before-this was super informative.

backend course backend.win 0:00

Never heard of this concept. I like it, it seems like a very clever way to be efficient. However, as you mentioned... proxies and other middleware might not like it, and to the client they might not be able to distinguish between a middleware timeout or the service itself timing out. Perhaps this could be mitigated the first time it happens by the client itself specifying an ever-decreasing timeout via headers or something until it finally hears back from the service. I'm only at 10:45 right now watching at 2x speed, so maybe it's discussed later ;-)

Please share roadmap frontend

Pointless rambling.

Hey Hussein, Thank you for all the good content that you share. I am a backend engineer with about 3-4 years of experience and the imposter syndrome is very real for me. I feel I don't know a lot of things which someone with these many years of experience should ideally know and I am trying to get over this feeling. One way I feel it might help me is if I start building good personal projects involving some of the core areas of engineering. I would love to see some content from you on what kinds of projects can a beginner engineer work on. Or anything you deem fit on this topic - personal projects or rather how to self-develop your skills (by self-develop I mean if you don't have the opportunity to work at a big organization with hands-on experience in different technologies). Hoping for you to check out this comment. Thanks!

There can be n number of CAs across the world and every website I visit can have a different cert chain so how is it possible for anyone to predict those many cert chains to have it installed in my OS?

Excellent video