When and when not to use Node.js - Node.js Basics [06] - Java Brains
HTML-код
- Опубликовано: 23 мар 2020
- Have you seen the new Java Brains? Check out www.javabrains.io now for awesome courses and content!
Understand the core problems that Node.js was meant to solve and why it is a good choice for certain applications and not for some others! Learn the strengths and weaknesses of the Node.js platform.
Java Brains website: javabrains.io
Access the full course playlist here:
• NodeJS Basics
#JavaBrains #Node.js #JavaScript #Tutorial
Having an explanation of the technology before diving into the code is extremely useful. A lot of youtube channels don't explain anything.
absolutely
Get "Learn and understand NodeJS" by Anthony Alicea on Udemy. It's a gem. Takes apart NodeJS and explains its basic behaviors.
Others can be, Unapologetically greedy.
Hey, you need to do a series on "When and when not to use".
Very interesting :)
Yes that's a good suggest
I have been working with node js for a while but this tutorial is one of the best tutorials out there. Thanks for sharing your knowledge
That's the best "how, why and when" video about programming languages I saw by this day. Well done!
Dear Koushik, You are outstanding as always. I could not find a single person who speaks technology as simply as you do. I have been following you for more than 7 years now. I truly appreciate your efforts. Thank you.
One of best explanations of event driven model of Node.js
Eagerly waiting for the next video
Great video, one thing to add is it's commonly used in distributed systems. thanks to its non-blocking ability and asynchronous behavior.
this is why is it called node after all. because a nodeJs server is just a node among other nodes.
when to use: "do this then this, then this, then this"
when not to use: "generate every prime number up to 100000000000000000000000000000000000000000000000"
At that point, you would be using C lol
I tried to do that once.
wow being more than 10 years in web development... I like how simply you explain the details! keep moving bro, I'm definitely following your tutorials and moving to node js from the programming language I'm using right now, also I subscribed to your channel :)
I think that for this video is great at explaining basic concepts in a simple way. Good job!
Having experience of working in Node for last couple of years, but some info in this tutorials are complete GOLD
NICE lets make this lockdown a little educational and knowledgeable
Great Explanation. It is important, not only to know the code language but also learn which code is better to put in use depending the context of the app you are going to develop.
Thanks for this. I really enjoy the long form, in-depth discussion on one topic.
Man you are the best and let me tell you that listening to you is always blissful and let me tell you that you are an awesome teacher and always make things simple and cool for listener's. Thanks. 🙏
you covered this SO WELL... like you hit all the proper keys and put it all in a easy to digest manner, I will be using this to explain this to people D:
I really appreciate your explanation! I’d love to hear your take on comparing node.js to other options like python, php, etc. But thank you again for this video.
When NOT to use Node.JS:
When your client insists you use PHP.
hahahaha
i bet you "work" with wordpress
When your client insists that you should "destroy an already existing wordpress solution"
so true
LOL
that was really great. I was confused whether to use node.js or not, but now I am clear :) Thanks! :)
You are a gem for Providing us with this example. Thank you!!
Thank you for talking about Node.js. I would love if you get into some of the advanced capabilities of Node.js! Thank you.
Been following this guy since I started, spot on
And nice touch on the c/c++ node backend
Simple loved it... Clear explanations with proper examples
A great explanation that i've been looking for,awesome!
This is the best tutorial I have ever seen.
Very clear explanation sir. I loved every minute of this video and walked away feeling like an expert.
As someone new, you explained this so well. Thank you!
Loving you since your first video of servlets. You shine 😎
Thank you for this video! It was very informative!
In fact node can use multiple cores if needed. But it is hidden from the developer's view and taken care of by libuv.
You are a life saviour Mr.Koushik !
Would I be correct in saying that NodeJS handles jobs equivalently as using SelectionKey and Selector in java?
I learnt mern from online courses but understood the core architecture/logic from this video.thankyou very much
It is pleasant to find Java devleoper who doesn't just blame javascript) Thank you for this movie!
I was also Java Programmer and loved to write java programs... But since I started learning NodeJS, I really get in love with Node.Js specially with Nest.JS Framework...
Most informative I've seen so far...
Thank you
What i retain is that Node is well designed for I/O intensive systems, certainly the reason of its success in widely used microservices architecures. Gonna learn it. Thanks!
You deserve more likes and views for the great analysis on node in this video.
Can someone link the time where he talks about mutual execution, conditionals and shared memory?
Thank you for sharing! Very helpful! God bless you!
i was searching for this and found your video.. that's great
Thanks a lot for the explanation. Its really needed when diving into it.
compute intensive is no more problem for nodeJs due to Worker Threads on node 10.5.0 .
Still it carries the javascript overhead which is quite negated with io bound concurrency. And 70% of the real world business require that io bound concurrency.
@@manikanth2166 yeah it really depends on the size of the project/business as well. Node is so quick and painless to develop for that it's worth using for almost any app that will have a small userbase.
I've even just gone and created microservices with GO that sit on the same box and communicate with the main node web server through a REST api.
You can always use process manager like pm2 to spawn multiple instances of your node app and then act like a load balancer.
this is a good enough approach, although processes are heavier than real multi-threading. Worker threads solve this well but they have a funny api.
You are the best teacher online. Like 👍
You can make node multi thread if you want to. It is not usually that way but there are modules that make it as multi thread as you want it to be.
extremely great explanation. thank you very much.
Hi, what do you think if compare to multithread + async ability for example asp.net core ?
i really enjoyed this explanation, love it
Great explanation. Thank you!
Thanks for sharing!! Amazing Job! Could you do a video about front-end architecture and when to use it? :)
Awesome job as always!
Really well done video. Easy to follow. You're interesting to watch. Useful information. Thank you.
Thank you very much it really gave me clarity
Very well explained!
It was really helpful! Thank you!
very good explanation! Thanks.
Very useful explanation ... This video should be used also to explain Single Vs Multi-threaded systems, not only for Node Js.
Great Job (Y)
How nice that the color of your jacket is the same as the color of the font and the frame in your presentation
Great! Very clear! thank you.
Good work! Can u make this kind of video about Django framework?
Just want to ask, if I run 2 files with Nodejs. e.g. $ nodejs myserver1.js and $nodejs myserver2.js simultaneously, does it run each file on its own thread? e.g if I perform intensive computations on running myserver1.js they will will not affect the running file myserver2.js ????? THanks!!
i like this series when and when not ! :D "Just because you can do it doesn't mean you should do it"
Thanks and I really like you work...keep it up .
Sir then
Os internally allocates threads to multiple callbacks.
Hi excellent resource, i have a question. When talking about node and that computing intesive task, are things that node isn´t good for, i was wondering, about promises ?. If we wrap that computing intesive process into a promise, we wont block the main thread and we can still be able to build those types of app ?
Cruz Ortiz No, promises are nothing but a syntactic sugar on top of callbacks so it basically means whatever computation heavy task you wrapped inside promises still have to be executed by node’s main thread only
I'm with you since you uploaded first springboot video.
Waiting to learn Promises and Streams from you.
Can yu do a video on springboot multitenancy with oracle or mysql db..
The ammount of info in here is amazing =)
Cool video, thanks man!
Sir can you please tell me why we use node.js where we have so many options like java . Net.
Very good explanation.
Thanks you so much for this video.
You teach really good, thanks
I like how your hoodie colour matches the purple of the border and font.
you got one mistake there, asynchronous doesn't have anything to do with multi-threading. it is possible to do asynchronous calls in a thread pool. you can have threads execute mutiple event loops, process non-blocking i/o calls, and no thread have to wait for IO (unless you call synchronous/blocking operation).
asynchronous i/o operations are offered by the operation system, there is no rule dictate you need to use single thread model or muti-thread model to use these async API.
But, I guess, it's often put like this - if you have a multhithreaded framework, go ahead and use the luxury of a blocking model. The resulting code is more clean and decoupled.
@@piotrgoabek6166 .net support non-blocking i/o api out of the box with async/await (sort of like coroutine). the benefits of coroutine is that you have a nice synchronous-like control flow, look really clean, easy to reason about even in multithreaded environment. other example is boost::asio in C++ support coroutine, callbacks, proactor model, blocking and non-blocking operations and possible to decouple with template.
it's often like this, if you have a multhithreaded framework, go ahead and use the luxury support of non-blocking api, the resulting code might be efficient, might be clean if you know what are you doing.
the point here is multithreading with asynchronous is possible, there are framework support these thing.
to be honest, i think people that write multithreaded program will use non-blocking i/o if they can, their concern is performance. you can write clean, decoupled asynchronous code in multithreaded, because again these things aren't really relate.
He did not conflate the two though. He used examples of typical situations where synchronous calls are used with multi threading and asynchronous calls are used with single threading. His diagram of a thread pool even shows an asynchronous call being made
when exactly did he claim this?
@@jesuslovespee 6:50 , 7:17 "it has to wait".
he did mention at 7:26 "thread pool with `synchronous` execution has that kind of behavior". he tried too hard on selling nodejs's singlethread model by compare it with a very inefficient multithread model and failed mention about multithread with asynchronous.
yes, he didn't claim mutlthread models can't do asynchronous. I won't discuss this anymore, he didn't even bother to comment, so it's a negetive-sum game.
Great video, thank you! small request - can you please create playlist of Node.js Basics so it will be easier to follow?
Thnaks
This channel should be renamed as tea with java brain... Ur doing awesome work love from Pakistan
Very well explained. After watching this video had subscribed to that channel for upcoming videos.
Please do a series on Design Patterns, if possible. Thanks
So for an MMO, Node isn't / wouldn't be such a bad idea as long as keeping track of requests, responses, and other such actions (loops through any relevant entity like players, enemies, etc) are only done with small calculations?
The Hero we need but don't deserve. 😢Thank you so much good Sir. Great explanation
You are the best man!
You could use node js for blocking operations if you create copies of the node process, is that right?
this content is awesome!!🎉 Thank you so much 😀
Just one question --
In multi threaded programming language, how number of thread pool is defined? Is it predefined by language or is configured by developer only?
In any case, what could be the maximum number of thread pool can be created? Is there any parameters for it?
Please answer if possible. Thanks
you have the art of explaining
This content is really good
What if you wrap the calculation intensive operation in async function?
What about languages that can multi-threads with async functionalities?
It queues up async functions. The best thing you can do it offload the work to host OS with worker threads.
Very Helpful!
You have a very cool personality and style that I like !!!
can you please suggest, what should be used Where nodejs is not a good option ?
Thanks to RUclips algorithm for suggesting your channel to me!
hey nice explanation dude, specifically when not to use, lovely :)
Great explanation!
perfect explanation.
very nice explanation
Great info Thanks.
You know you can fork new threads for processing intensive tasks in node.js, right? There's also wasm to turbo mode your processing if you need it.
Just curious on your thoughts of using node.js these days over netcore 3+?
I don't understand the for loop example. Wouldn't that be single threaded on any language? When you say a thread is that the same thread that CPUs mention in their specs?