Please keep making such videos.. Really helpful!! 🙏🏻 Very well explained admin !! God bless you 😇

Thanks a ton! So helpful.

Hi , Why have you stopped making videos , they are such a gems and helping alot of youngsters.

Nice.. could you please cover IDP bride

Awesome explanation and i always used to wonder while going through producer-consumer code, that why we use while statement to block the threads. Finally got the answer. Thankyou🙌

Want more playlists like this Sir, you made our life easy

Great explanation about the spin locks I came across.

pls do continue to upload more vedioes like this.. your java concurrancy playlist helped me a lot to understand the multithreading concept.. pls do contine to upload more java indepth vedioes . thank you

Please add new videos. These videos are best to understand concepts.

I'm facing a scenario, where the threads could read the shared variable without volatile keyword, @defogtech can you help to given an example on volatile usage, public class Example implements Runnable { private static boolean gate = true; @Override public void run() { while(gate){ //print something } } public void setGate() { gate = false; } public static void main(String[] args) throws InterruptedException { ExecutorService service = Executors.newFixedThreadPool(2); Example ex = new Example(); service.execute(ex); Thread.sleep(2000); ex.setGate(); service.shutdown(); } }

Buddy you should be collecting my parallel programming in java professor's salary. You are the greatest of all time, you're getting me through college. Every single one of your videos has helped me immensely.

Thanks for the video! I need a clarification. Bulkhead pattern and circuit breaker pattern are two different solutions to prevent the same problem (i.e. a microservice, say, an order service becomes unavailable after sometime if another service, say, payment service takes too long to respond to the requests from order service.). Is my understanding correct? If my understanding is wrong then please explain the difference between the problems prevented by the two patterns.

Wait, I'm consufed: on 01:03 you were saying there's no API to stop a Thread, while on 09:26 you are calling "stop()" method of the Thread class. So, is there API to stop or not?

Thanks a bunch for this video. Nice explanation. One request - can you explain the data integrity issue mentioned at 02:54 with an example for my clarity please?

Fire

Awesome video, it would have been great if you could add the link to the source code too.

Hi Sir, Your videos are more informative and upto the point. I am not sure why now days there no new videos or topic not getting upload. Please continue with atleast 6months 1 topic

Also enum initializes its instances eagerly right?

Can we also say we are making it volatile so that no thread ends up looking at a cached value which might still say that the instance is null and that thread ends up creating another instance?

Great Videos is it possible to cover the life cycle of Thread and its methods, how it works, ExecutorSerivice -> how it works internally, how it will reuse the same threads, in the prospective of the code

Your playlist on java concurrency is by far the best out there on youtube

It's the simplest and most descriptive tutorial about oauth 2.0 I've ever seen. Thank you a lots. Excellent

Your videos are very use full thats helps us lot. But one request can we get your ppt or blog where we can have notes

Sir please make new videos

Good one

Splendid and Explanation with an intoxicating voice.

best explanation

Great videos as always, thank you so much for all the learning content here

Awesome explanation

Hi all i want to understand little further.. now incase of spring boot application we are not creating any executors service rite, are these created internally by application itself? As he told that DB , Network calls will utilize lot of CPU.. I have one more doubt what is process id and port num

Top tier tutorial video

import lombok.SneakyThrows; import java.util.LinkedList; import java.util.Queue; public class ProducerConsumer { static class BlockingQueue { private final Queue<Integer> queue = new LinkedList<>(); int capacity = 5; @SneakyThrows public void add(int i) { synchronized (queue) { while(queue.size() == capacity) { queue.wait(); } Thread.sleep(1000); queue.add(i); System.out.println(queue.size() + "Producer Thread"); queue.notifyAll(); } } @SneakyThrows public void remove() { synchronized (queue) { while(queue.isEmpty()) { queue.wait(); } Thread.sleep(3000); queue.remove(); System.out.println(queue.size() + "Consumer Thread"); queue.notifyAll(); } } } public static void main(String[] args) { BlockingQueue queue = new BlockingQueue(); for(int i = 0; i < 10; i++) { Thread producer = new Thread(() -> { queue.add(3); }); Thread consumer = new Thread(queue::remove); consumer.start(); if(i % 3 == 0) { producer.start(); } } } } we can do something like this not making things complicated.

Please please continue video making😭😭..it's a GOLD

In love with the content..please resume the video making. It will help a lot of people!

This one is really good

Nice explanation, thank you!

thanks for the explanation .

Nice presentation. Clear explanation.

Hats off to ur efforts and elegancy. You have earned a subscriber.

Beautifully explained. You make everything very simple yet covering all thats relevant to the context. Please keep up the good work that benefits millions like us.

At 9:43, why do we put the clean up process in Service4? How do we know other services have consumed `User` when Service4 runs? Don't all the services run asynchronously?

9:02 CompletableFuture.allOf() is a blocking call, allTasks.get() is not useful. Any other ways to implement the requirement?

Awesome explanation !

Good video on Api Gateway. Your laser pointer is good. How to use that in my system. Please help.

This video has shown me true power of CompletableFuture

This is 1 video which explained me Future vs Callable Future clearly out of many other videos

It is really easy to follow all your explanations. Thank you for doing this!