Guidance for multithreading
I've recently completely core Java course, worked on a few small projects with Java and jdbc. And now completed multithreading, and understood most of the concepts how to use but:
when to use this concept, when to create threads and apply all other things.
how does using this thing make my project easy.
how to implement in real world projects and executors framework too. I've tried to search projects on YouTube dealing with multithreading but couldn't find even 1.
Could u pls help me by recommending some projects (for a beginner) from where should I improve myself.
18 Replies
⌛ This post has been reserved for your question.
Hey @Deorteur7! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.
one more doubt: should i actually put effort learning multithreading or focus on other concepts ?
Multi threading doesn't make your project easy
It actually makes it a living nightmare
Generally speaking multi threading is used when you have some very heavy operation to perform
i see, wt would u recommend me to learn
Or if, for example, you are dealing with some GUI framework where you need to run some job without blocking the UI thread because the entire program freezes
got it
Honestly unless you really need it there's hardly a reason to use it
It adds a pretty big layer of complexity to your project
I'd suggest you simply learn to get a sense for when its necessary to use multiple threads
i get it, well wt should my roadmap be for full stack projects
i learnt oops, jdbc, collections
then wt ?
Well I suppose for full stack you should probably learn the front end
I suppose you can try to make an http server that provides some service
You can write the front end in whatever
If you want it to be in the browser its probably gonna have to be JavaScript or typescript
Or whatever other language that can transpile to JavaScript
Just pick some full stack project you find interesting and make it. That's the best way to actually learn something
I'd say that in general, you'd use multithreading when you need to
as already mentioned by nikcho, one example is GUIs where you don't want an "App doesn't respondiing" dialog
another example is webservers where you typically want to serve multiple requests concurrently (you don't want users to wait for the other users loading the site) - but for this, frameworks are typically managing the threads
or if you want to do make more efficient use of your CPU and do two tasks at the same time
But it's important to consider that the annoying thing with multithreading isn't the part about creating multiple threads - it's that there are a lot of things to consider to ensure your code doesn't break when your code runs concurrently - for example if one thread assigns a variable, other threads might not see it and read the old variable
Yeah, another example might be something like an asynchronous operation with progress updates in your back end. I had such a case recently. An HTTP request to request a folder copy from one location to another. What you might do is start a thread to perform the copy and return an address to query the progress of the copy.
that probably falls in the UI category tbh
or the webserver thing
The folder is on the backend, its something like a file server
There's no way the front end would know the progress unless it can query it in some way
And it can't do that unless the back end provides some endpoint to do so
In any case, threads are a pain. My advice is to avoid them like the plague when possible
It's no coincidence JavaScript runs an event loop and is single threaded
Given that this is a Java server and not a JS server, I consider that as the UI thing
I'm just talking in general, the JavaScript is just an example
I don't think there's an argument against "multiple threads are a pain to deal with"
And if there is I'd love to know it
you wouldn't multithread something just because it's a network request
Yeah, as I said it's simply an example.
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.