Watched multiple videos over this topic, was confused. But this 7 min video explained everything what's needed, implementation, alternate approach & proper difference! Thanks dude!
Hey Mehul, learning every day something new related to tech from your channel is very informative & useful. the way you explained the topics is just awesome especially liked your explanation using whiteboard it helps to visualize the things. KEEP IT UP. Thank you.
Can we have a video for how to write a programmers guide document. Would really be pleased. How to write api/sdk documents that will help developers save time and get clear information
The video was really good and informative. The part that u said "the way u make stateful, stateless is that u actually cheat by..." Was what I was looking for. And just a suggestion, It would have been great if you had mentioned the name of the 2nd strategy that u described for scaling stateful apps which is "sticky session" so that people can search that
if you store the session or state in cookies, why can't it be serve on different instance.. The data is persisted inside the request headers and not on the server. no? 🤔🤔
I watched this video till the end! Thanks for being so clear and practical in your explanations Mr. Mehul, I learn a lot from your videos, even the short ones. Keep it up! I wish you an amazing day!
I really like your presentation style. You clearly know your stuff. I might suggest a minor point of clarity, however. When discussing state and parallel / multiple servers, it would help those lacking experience to explain the overall point of managing state. That is, the single point of truth necessary to make the rate limiting logic work. Similar to the point of a database server, for example. Just get that basic concept across in the beginning so the alternatives and limitations become more obvious. Nice work, I like watching your videos.
So as you said we can send special cookie back which may contain address of server. But here again that client machine when they makes a call they again need to send the cookie back So any how it is similar like token based authentication. Here I can suggest we can check the ip of request if it's coming from same ip then give that request to same server that we need to implement at load balancer level. Please correct me if I am wrong. Or else you can add more to it. Its really nice and clean video 😊 Thanks
Idk if you’ve done a video on this but could it be possible to do a video on authentication ? Like tokens, and sessions and cookies. Where to store the authorized tokens, where the authorization logic is done. Other protections and rules as well For example if I’m using firebase, where is the token stored? Do I send the whole token back to the front end or just the User ID portion back to the front end? Really confused on this
Your redis instance would almost always never be in the same computer as your other systems in a scaled setup. You’re right that redis keeps things in memory but when external systems need to read/write they need to access that redis instance over network
One complain : You said about a wide range of Software or web development...But you don't said the basic enough...Its bit hard to understand...This video is great but some are hard to understand for beginners
Watched multiple videos over this topic, was confused. But this 7 min video explained everything what's needed, implementation, alternate approach & proper difference! Thanks dude!
After another video on the subject failed me, your use of a practical/real world example is really what made this click for me. thanks!
Hey Mehul, learning every day something new related to tech from your channel is very informative & useful. the way you explained the topics is just awesome especially liked your explanation using whiteboard it helps to visualize the things.
KEEP IT UP.
Thank you.
Thank you for the amazing explanation. This really helped me a lot! And I did watch the video until the end.
Can we have a video for how to write a programmers guide document. Would really be pleased. How to write api/sdk documents that will help developers save time and get clear information
I watched this video till the end 🙏
Thank you so much 👍
The video was really good and informative.
The part that u said "the way u make stateful, stateless is that u actually cheat by..." Was what I was looking for. And just a suggestion, It would have been great if you had mentioned the name of the 2nd strategy that u described for scaling stateful apps which is "sticky session" so that people can search that
learnt something new today . Thank you :)
if you store the session or state in cookies, why can't it be serve on different instance.. The data is persisted inside the request headers and not on the server. no? 🤔🤔
It's not about the cookie, its about the data stored in memory of the server (the IP address counter in this case)
I watched this video till the end!
Thanks for being so clear and practical in your explanations Mr. Mehul, I learn a lot from your videos, even the short ones.
Keep it up! I wish you an amazing day!
I really like your presentation style. You clearly know your stuff. I might suggest a minor point of clarity, however. When discussing state and parallel / multiple servers, it would help those lacking experience to explain the overall point of managing state. That is, the single point of truth necessary to make the rate limiting logic work. Similar to the point of a database server, for example. Just get that basic concept across in the beginning so the alternatives and limitations become more obvious.
Nice work, I like watching your videos.
I watched this video till the end!
Very good video!
Great work explaining this concept
Simple and clear explanation. Thankyou
I WATCHED THIS VIDEO TILL THE END!
❤️ Thank you so much Codedamn❤️
Bro big like! Love the explanation!
So as you said we can send special cookie back which may contain address of server.
But here again that client machine when they makes a call they again need to send the cookie back
So any how it is similar like token based authentication.
Here I can suggest we can check the ip of request if it's coming from same ip then give that request to same server that we need to implement at load balancer level.
Please correct me if I am wrong.
Or else you can add more to it.
Its really nice and clean video 😊
Thanks
Bro I love you man. Keep sharing yo knowledge!
watched ill the end. really good stuff thanks Mehul.
I watched this video till the end. This was very informative. Thank you very much.💡💡💡
Watched this video till end great one awesome work
Nucleya of coding uploads every single day!!!!!
Excellent explanation.
Im literally waiting for channel to hit 2lakh subs
👀
@@codedamn its been soo long since you have consistently posted every day
Still that number is elusive 😭
Idk if you’ve done a video on this but could it be possible to do a video on authentication ? Like tokens, and sessions and cookies. Where to store the authorized tokens, where the authorization logic is done. Other protections and rules as well
For example if I’m using firebase, where is the token stored? Do I send the whole token back to the front end or just the User ID portion back to the front end? Really confused on this
Very very useful topic covered with ease. Thanks a lot ✌🏼❤️
But redis is in-memory right and uses ram . But in the video, you explained redis cache is slower because of tcp network. can you help explaining ?
Your redis instance would almost always never be in the same computer as your other systems in a scaled setup. You’re right that redis keeps things in memory but when external systems need to read/write they need to access that redis instance over network
Do you teach all these stuffs in your courses?
Watched till the end... Did so many times for your other videos... But it's the first time I'm saying this.
❤️
I watched this video till the end!
what if Redis has multiple instances?
this is gold mine...
Watched till the end :)
I WATCHED THIS VIDEO TILL THE END!
Thank you so much
Very informative
More videos on security pls...
Interesting!
Great!
One complain : You said about a wide range of Software or web development...But you don't said the basic enough...Its bit hard to understand...This video is great but some are hard to understand for beginners
This is high level overview. It is mostly software architect thing. :)
I watched this video till the end
I watched this video till end
I watched this video until the end
I watched till the End ...
❤❤
I commented many times but never gets an response
Hello 🙌
I watched this video till the end. xd
Always first ❤️❤️
I WATCHED THIS VIDEO TILL THE END!
I watched this video till the end
I watched this video till the end