Amazing content 🎉❤

Project Loom has led to virtual threads, with a virtual thread per request and a carrier thread that is actively executing. In Java 21, synchronized locks and native calls block a carrier thread. In Java 24, only native calls will block a carrier thread.

Waiting for explainers on other databases

Goat

very well explained , thank you !!!!!!

Great Learning channel.

your each video is so much Informative. Thankyou:)

bhai ne api gateway ko hi monolith jitna bana diya mast video <3

Wonderful

Thank you so so much loved it 🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏

Just hit the subscribe button! Well done with the video. Looking fwd to seeing more content from you.

This channel is goldmine.

You are the only one explaining in depth , clarity the complete execution of Java Programs. Hats OFF. Thank u

Another gem.

This video is a rare gem.

Wow this is great videos with great explanation really wonderful Thanks a lot sir

brilliant

Can I get the documentation of this whole playlist?

Amazing explanation, great playlist for clearing concepts!!

Good video!

Aren't you complicating by adding relevent data like product details to the cart table? Here ,hwo do we update product table - when we update product table, should we check all places the product details is there and update that too ? This will be a hige task ! Do not understand the actual benefit over the added complexity.

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