django Architecture - Connection Management 

I agree

Feel ya, men must do work to be men

'hours' is peanuts when it comes to content creation lol

I feel like he is also one of the few tech RU-vidrs who knows his stuff inside and out. There are definitely others but the majority of tech channels are new grads reading snippets out of the documentation.

you actually are optimising reads. By having a cache pool and pluging it in with your application leverages the cache to fetch responses faster. at some extent mongo or mysql also uses a lru buffer to bring in the recent read pages into memory and thus saving a lot of disk reads as ordered. As per your specification you want to do it in the previous hop by putting a cache layer in between your database layer and your api layer. But you always have to trade latency with cost.

Lol of course. I know just Django,I download free frontend templates, then chatgpt helps me write js fetch requests to query my backend api endpoints until I starting doing that myself too

@@isegofficial oh Oka. I'm learning django currently. Just started the class for django and I only know basic python by now so I was really scared 😭 I'll learn the other languages once I'm done with this

@@isegofficial also ,is there a possibility of getting job after I have full django knowledge?

@@Namjoonsbonsai of course. Don’t let the internet deceive you. Just build stuff. Like 2 good projects and upload on your GitHub and linkdln

​@@NamjoonsbonsaiThere is no possibility, nowdays companies expected Fronted, Backend, Docker, Kubernetes, Apache, nginx, FastAPI bla bla bla

I'm guessing multithearding in python deserve a video of its own. Django usually used behind a wsgi server (nginx, gunicorn etc.) In a way you will have multiple processes with single thread on each process.

Your inbuilt http server isn't a process manager, what wsgi does is it taps into process management and separates application execution. Allows separating environments, application context and much more stuff that is required to invoke application efficiently and securely while keeping resource usage minimum. Implementation may vary depending on what server you are using but simple idea is, it's webservers responsibility to sandbox request response lifecycle and wsgi provides that barebones for any application and allows it to be build on top of already solved problems when you are writing web applications. This is same as (but not equal to i.e. similar to) using express in node, php-fpm, tomcat / websphere or any other application server, they are server appa helping in management and hosting of application itself while keeping them isolated from host system in one wya or other and providing specific standardised API at your application layer where you actually write business logic.

@@MaulikParmar210 thank you!

On another note is that from 4.1 it support async orm and views so yah async is supported there as well

yep it is the OS's work to schedule and context switch processes

correct pgbouncer proxy helps this.

use starlette?

Nothing happens. You are still limited by the number of threads, and since django only uses one connection per thread, your thread is still going to sit idly by waiting for a response from the db server. (PgBouncer would have helped with the first problem mentioned in the video, that is django by default creating a new connection for each request if django didn't in fact have a setting to enable persistent connections, but does nothing to help with the second one.)

The video did explain the architecture to you.