Congratulations buddy for your new job . Good to hear that 🥰

Its really annoying why the Java Techie doesn't add timestamps

Shiva my role is here to explain the concept .if you understand it correctly then it's good .

@@Javatechie As a presenter imo u need to care about user experience. Timestamps really help in that area. Eventually its ur call. BTW nice content. Recently found this channel. It would be more helpful to browse through the content more fluidly via timestamps of contents. Thanks for reply

@@codingshiv1670 I completely agree with you. Going forward I will take care this for longer video

Hi Sri , yes will do that 👍

Thanks buddy 😊

Why don’t you like it 😂

@@Javatechie No, on the contrary, I like it :)

Yes I agreed @Abhishek Dubey It would be great if this explain in debugging mode

I understand little in English but you speak slowly and then for me it was much easier, thanks

Thanks vinod ☺️. Noted your suggestion

@@Javatechie thanks❤

Am not aware about this DeferredResult method

I think the wait() method can distinguish the thread call.

Custom thread pool

Hi , I believe Rather than increase thread count we can resuse them

Yes exactly , even though there is any exception in any thread it won't stop your execution . But there is better solution to handle fault , will do that

You get more control while using ThreadPoolExecutor.......like setting up core pool, max pool (understand these two) You get the queue feature. In the simple one it creates one thread for each task, no concept of queue. Threadpool is also resource friendly since it uses pool and dont just create a new thread for each new task. Also there is a bound mechanism which prevents it from creating infinite no of threads. You can set up the thread names too in threadpool...and manage the thread lie cycles in a much better way. You can use the Simple one if you are working on a personal or small project but in a company or for any big project you should use ThreadPoolExecutor

You need to join or combine all threads to get results

Yes reactive programming is more popular now a days .I will start a brand new series with it .

Yes this is how we should use completableFuture

One is the framework that automates the process that is a spring framework and ComplerableFuture is just a way to perform concurrent flow

Queue size meant to hold waiting task in queue Who ever thread serving 101 and 102 request once any one release he will pick 103 task in queue Note : queue will not always full with task , if task executed then it will release from queue and new task will add to queue in FIFO manner

@@Javatechie got it now. thanks 😊

Is data present in your database

Last get method was actual implementation of multi threading

Once it serve 5 request , then who ever thread is free will go to task/request queue then will process further

I believe the outer try is meant for exception handling while inner try is just meant to avoid writing close() method for the buffered reader.

Executor is an interface however ThreadPoolTaskExecutor is it's implementation

@@Javatechie it's my mistake actually I import executors which is class that's why I get error

Always recommend to use multi threading in read operation not in write operation

@@Javatechie but how does read operation does not go for multiple threads even tough it is annotated with async annotation?

@@tejasnakhateYes I not understand why we need to explicitly create several CompleableFuture objects when calling findAllUsers in order for multiple threads to be used but yet for saveUsers we do not need to and @Async annotation is enough for saveUsers but not for findAllUsers

Did you configure Lombok in your IDE ?

@@Javatechie I was able to figure out the issue. The problem was not with lombok, it was with H2 DB app properties. I did not configure it, so the DB connection was not made to create the table. But Thank you for replying as fast :)

did you find any solution

This is an IO intensive task so time taken will be more or less the same no matter how many threads you create because records will still be inserted one by one only cause DB has to maintain consistent primary key IDs.

@@ShinAkuma Sorry mate, but I didn't understand, could you please elaborate?

​@@beeam1791I've got this 1 so basically what he means is, note that the database has an ID column in the User table, and the id column is the primary key. Primary keys must be UNIQUE, no 2 users can have the same primary key. So, imagine you have 10 threads each inserting some of the users from the list of users sent via the MultiPartFile like in this video, if thread-1 and thread-2 are running concurrently, thread-1 trying to insert a row into the users table for "John Doe", and thread-2 inserting for "Joe Smith", for example, but thread-1 sets John Doe's ID column to value of 1, and thread-2 sets Joe Smith's ID column also to 1, this cannot be, no 2 users can have the same ID. Therefore, the insertion of users must be done sequentially to ensure that no 2 users are inserted with the same ID. You'd likely get an exception if this happened, anyway, because ID columns are intrinsically unique.

Yes

There willl be two threads you will trigger.. because the pool size is 2 right.. if you want to check before return you could use some thread sleep then you will find it.

Thread is not splitting the task, it’s you who are splitting the task and assigning it to different threads. Each time you call an async service method it will be executed on a new thread.

If you found my response helpful or you have any query i can help, you can connect with me on twitter: @biswajitojha430

He is just showing an example that if any case you are running dependent services on different threads and you want to join the result then you can follow that step, else if you are running independent services there is no need to join

If you found my response helpful or you have any query i can help, you can connect with me on twitter: @biswajitojha430

No adding @Async in method 1 is absolutely fine but make sure all 3 method return types should be either void or Completablefuture

@@Javatechie ok thanks...i will try this.... thanks for all ur videos and knowledge sharing...i regularly watch ur videos and i appreciate ur efforts u put in knowledge sharing