Java ExecutorService - Part 1

Chapters:
0:00 Java ExecutorService introduction
0:28 Java ExecutorService example
4:02 Java ExecutorService implementations
5:46 Java ThreadPoolExecutor constructor explained
8:16 Java ExecutorService methods
9:36 Java ExecutorService submit(Runnable) method
12:12 Java ExecutorService submit(Callable) method
14:23 How a Future object is connected to a task
15:23 Java ExecutorService invokeAny() method
18:10 Java ExecutorService invokeAll() method

Java ExecutorService - Part 2

Java ExecutorService Using Virtual Threads Internally:

Java ExecutorService - Text:

Java Concurrency - Text / Video Playlist

[MoZaHo]

Best description and video of the ExecuterService on the internet. Helped a great load. Thank you

[karthikgsarode]

Detailed, to the point explanation. Thanks a lot Jacob!

[fatihmehmetkose]

Thanks Jacob! this is the best explanation of ExecuterService and Callable I have seen...

[BtXFWkyZBtXFWkyZ]

Reminder is set, thanks for the content sir

[mdshafi]

Sir, Can you please make a video or 2 on deadlock situation in multithreading and how to handle them in java ? Your videos are very helpful.I understand multithreading well by watching your videos

[sumanshekhar]

I think invokeAny() starts executing all the task in the Colection, and returns the o/p of the task which completed First.
After this all the tasks are canceled.
Btw thanks for the awesome explaination.
We want more of your knowledge :p

[Dayakar-vidh]

Thank you sir, For clear cut explanation.

[tomasma]

Thanks a lot for these videos. I am programming few years in Java but there is always something new I learn from your videos or from your web site. You definitely deserve more subscribers. Just an advice, maybe instead of old way anonymous classes you could use lambdas. But anyway good job and keep doing!

[Jagan]

It was very nicely put and easy to understand

[smitmandavia]

Thanks a lot for the video and other videos in this playlist. They are really useful.
I think one small suggestion is to clarify that how is this different than thread Pools (explained in previous video). I guess Thread pool was our own simple implementation whereas this is an inbuilt and more nuanced version of it.
Please correct me if I am wrong or missed anything.

[mouradlaraba]

Thnaks a lot sir your courses are very helpfull, you are very generous in sharing your knowledge with us thnaks a lot

[LuneAgent]

Great Scott! We can get a result back from the future!

[강승윤-nw]

I love your tutorial web site and also like this video ! It's really helpful. Thanks a lot !

[ahmetbcakici]

Thanks for the content! It ıs really so useful and easy to understand.

[garimadhanania]

quick clarification: in the invokeany() call, it could happen that few of the tasks were executing and because of one of them completed and returned the result, the others were aborted? I mean there could be multiple tasks being executed on the different threads right?
If only one task is run, it might take a long time to return and that defeats the purpose of using invokeAny() right?

[roman_mf]

Hi Jakob, thanks for another excellent explanation. I have a question about invokeAny() - you say that it executes one task, but you also that the one that executes fastest gets to send its return value. How does "fastest" work in this case? Do all tasks in a collection run concurrently and they just race for who finishes execution first? invokeAny sounds almost like it just picks one task and has some logic of a failure in execution, like a timeout.

[devalshah]

Hey Jakob thanks you for such a detailed video explanation of the Java concurrency. I am not able to find this codes of Executor services in your github repo, is there anyway to get this implementations code?

[sam_paul]

Very well explained.. Thank you very much !

[csabadanyiko]

I really like your videos, great explanation for complex topics.
I have one question.
For invokeAll() you created a List<Callable<String>> then you cast it to Collection<...>. Why didn't you just define it as Collection<Callable<String>> in the first place, is there a particular reason?

[affeine]

Why do we have multiple ThreadPools inside the ExecutorService ? We still can specify number of Threads that ThreadPool executes so why do we need more than one ThreadPool ?