Multithreading vs Asynchronous Programming
Multithreading and Asynchronous Programming are two concepts, that people usually get confused with. This video explains the difference between multithreading and asynchronous programming using some real world examples.
Reference articles,
docs.microsoft.com/en-us/show...
www.ibm.com/docs/en/cobol-zos...
*******************************
💥 Thanks for visiting 💡 Nutshell. 💥
The channel focus on introducing software concepts, that cover area like Languages and Frameworks, Infrastructure, DevOps, OOPS and many more. Technical breadth is essential for full stack development and it is important criteria in most full stack dev interviews.
This channel helps you to become the jack of all concepts. 😑
It is difficult to understand the details of all technical concepts in shorter period of time. And it also tiresome to watch hourly long videos to understand the concepts. The objective of this channel is to introduce the technical concepts and explain the crux of those concepts within 5 to 10 minutes. It is up to you to go ahead and understand those concepts in details, if it interest you. The idea is to keep the video as simple and short as possible to just introduce the concepts and make the viewers understand the purpose and use cases for such concepts.
Feedbacks and comments are highly appreciated. 😀
Website: www.jawahar.tech
Linkedin: / jawahars16
Twitter: / jawahars_16
Instagram: / jawahar16
Very well explained, thank you! I have a question, Does using await when calling the asynchronous function discard the advantage of asynchronous flow? What is the best way to call an asynchronous function?
Thanks Krithika for watching Nutshell. 😊 Now to answer your question, asynchronous function behaves same no matter whether it’s been called using await or not. The purpose of asynchronous function is to return a promise which resolves in future. The await keyword is just a syntactic sugar. If the asynchronous function called with await, it only returns value after promise resolved (might take some time depends upon the function. So by this time execution goes to other parts of program). If the async function not called with await, you will immediately receive a promise object. You can attach a callback to it and get it executed once the promise resolved. Await is a convenient way to invoke asynchronous function especially to avoid callback hell.
Thank you for the explanation..I had this doubt in my mind for a long time, now it's very clear :)
Very well explained Thanks.
It was helpful, thanks
The explanation is very clear.
Behtareen 👏👏 explanation
Thank you for the detailed explanation
Excellent Explanation. Thanks 👍
Great explanation of the concepts in a simple way.
Thanks for watching Nutshell. 💡
You are underrated bro . I really admire the effort you put into your work. The quality of your content is truly exceptional. Keep it up.
Great explanation.
Very good explanation and Examples....go head with other videos' , thank you!
Thanks for watching Nutshell 💡
Great explanation with great example.
Thanks for watching. 💡
perfect explanation
Excellent
Good explanation, and one for the bird.
Great concept video Jawahar 👏👏👏
Thanks Shashi for watching Nutshell. 😊
Thank you sir
thank you i have multi thread program which connects multiple IP cameras in a Network but it is hanging when Network down or some time so how to change to asychronous please help
Well explained in a nutshell👏👍
Thanks Sabarish for watching Nutshell. 🙂
superrrr sir
too good explanation
Thanks that's helpful. But I still don't understand, say, in the boiler exmaple, if you only have one burner, you can't boil egg if you already boild milk, right? That happens with some single execution programs I am studying. How asychronous programming can be achieved in this case?
Nice explanations, thank you. Is multi-threading can be consider as one of the way to do parallel programming ?
Hi Kumaran Thanks for watching Nutshell. 😊 Multithreading and parallelism differs based on CPU cores available. One CPU can do only one task at a time even if you do Multi threading. (seriously, believe me 😜). So when you do multithreading on a single CPU, it just gives an illusion of parallel execution by switching between multiple tasks quickly (very quickly beyond our imagination 😱) But parallel programming can be real (not just illusion 🙂) by utilising multi core processors. With multiple CPU cores, you can literally execute multiple tasks at the same time. Hope it answers your question.
@@jawahar.nutshell Thanks again, please make a separate video explaining parallelism 🙂
Best video on this topic
Thanks for watching Nutshell 💡
Understood multi thread concept
Very good explanation! Clear, concrete!!! Thanks !
Thanks for watching nutshell 💡
best video ever thx
Glad you liked it!
So in asynchronous programing all the 3 request handled by single thread?
Useful video 👍
Thanks for watching Nutshell 💡
Really a greate explanation with exact analogy but , still I have a question what is exact difference between asynchronous vs concurrency.
asynchronous is a form of concurrency. By doing context switching btw the tasks we can achieve the concurrency.
Nice explanation
Thanks Rabeeh for watching Nutshell. 💡
Should mention that the usage of thread pools is to eliminate the cost of thread creation for each request as it comes in; the threads in the pool are already created and awaiting usage
Yes exactly. The time taken and the compute power to create threads can be reduced by using thread pool with pre created threads. Thanks for watching Nutshell. 😊
@@jawahar.nutshell Looking forward to more videos! thanks
If one await methids Depends another await method result? Then how
Nice explanantion
Thanks for watching nutshell 💡
Awesome
Thanks for watching nutshell. 💡
How many threads created in asynchronous?
there is no threads will be created for asynchronous but wherever you write await task delay or some actions that is when in order to resume from that place statemachine will internally creates one new worker thread which is called as callback thread for the main thread. This callback thread will be created internally by TPL it doesn't cost any resource ulitilization as we are not creating new thread externally using Thread t1= new Thread (Method); Summary: Async does not use any threads.
@@shobhamahadev118well explained