🔥3 Ways to break singleton pattern | Solution of Problem in detail | Hindi

[@nikkm2000]

Gajab Tiwari ji. Dil jit liye. Tussi great ho. 🙂

[@SreeTest-b6e]

Gazab ka knowledge diya sir aapne.

[@satendersingh2389]

Lecture dekh ke samosa khane ka Mann horaha hai

[@Romansoldier8888]

Timestamps 00:01 - Ways to break the singleton pattern 01:14 - There are multiple ways to break the singleton pattern 02:32 - Constructor in Singleton pattern 04:09 - There are two ways to avoid breaking the singleton pattern 06:19 - Two ways to break singleton pattern 09:15 - The solution to the problem is to overwrite the resolve method using Red Resolve technique. 12:52 - The method explained in the video helps in breaking the singleton pattern. 15:20 - Ways to break singleton pattern

[@utkarshrazzz9964]

Appreciable sir, waiting eagerly for your next videos on this series.

[@sgsenginier]

Awesome🙂Thanks.🙏

[@nikkm2000]

small query- at 6:12 min---I have done below---two different instance created..... Constructor constructor = Samosa.class.getDeclaredConstructor(); constructor.setAccessible(true); Samosa s1= constructor.newInstance(); System.out.println(s1.hashCode()); Samosa s2= constructor.newInstance(); System.out.println(s2.hashCode());

[@skaftab3954]

try this method: public class Samosa{ private static Samosa samosa; private static boolean objCreated=false; private Samosa() throws Exception { if (objCreated) { throw new Exception("One object already exists, you cannot call the constructor one more time"); } objCreated=true; }

[@preranagayke1464]

Hands of to your efforts

[@himanshubaviskar3966]

Good Explanation 😊

[@vaibhavkalyankar8650]

lol sir😃 @4:27 Ho gaya kaam tamam singleton ka 🤪 Nice sir

[@sumitsaini-lo8ic]

Hi Durgesh, are you sure that if you are checking for null condition in the private constructor to prevent breaking the singleton pattern it will prevent breaking the singleton pattern?

[@spider8015]

alag level sir aapka

[@azaankhan0311]

outstanding👍❤

[@ravijaiswal9231]

Samosha Khane ka man kar diya @Durgesh Bhaiya, raat hai milega bhi nahi🤤

[@subhamgoswami8607]

readResolve par detail video chaiye sir plz

[@ketank6864]

Thank you for awesome playlists

[@rohitjaiswal946]

Thanks for the great video, but I have one question, we are able to create multiple instances using reflection API even after adding the throwing exception in the constructor level. MyLazySingletonUnBreakable unBreakable2 = constructor.newInstance(); System.out.println(unBreakable2.hashCode()); //Here we are able to create another object MyLazySingletonUnBreakable unBreakable3 = constructor.newInstance(); System.out.println(unBreakable3.hashCode());

[@skaftab3954]

hi, i got solution to your problem you have to add one more static boolean variable, here it goes: public class Student { private static Student stud; private static boolean objCreated=false; private Student() throws Exception { if (objCreated) { throw new Exception("One object already exists, you cannot call the constructor one more time"); } objCreated=true;// it will be true when constructor created for the first time so from next time the constructor is called it will give exception }

[@MadhuKinneraDev]

Great video sir.

[@SaasBahuCares]

A video on java-17 features pls ❤

[@poorpanda9033]

Thanks a lot

[@qurashishebi7988]

keep it up

[@varnitajaiswal8569]

nice video sir

[@RishiRajxtrim]

great

[@rohandahiya6268]

What is double check locking and how is it better that single check locking ?

[@UmeshMane-k7d]

Hi Sir, In Singleton design pattern could you please explan why we need to use "volatile" concept.

[@suar_pilla]

bihari nehi janta

[@mishra.pritam]

so that al threads know the current value of samosa if made volatile

[@monasoni4881]

good

[@krishasharma_AJ]

Why we are using null check 2 times in get samosa method ?

[@NidhiSharma-sw4oz]

imagine both the threads are currently inside the 1st null condition. as soon as synchronised is there, thread t2 waits and t1 makes an object. now t1 has successfully made the object and come out of synchronised block. now t2 will go inside synchronised block. It would have tried to create another object BUT IT WAS NOT ABLE TO MAKE ANOTHER OBJECT BECAUSE OF 2ND NULL CHECK!!.

[@gamerauto]

@@NidhiSharma-sw4oz Wow Nidhi you're so smart, mamma would be so proud of you!

[@vinaychauhan7627]

Why dont we start our synchronized block from the first if condition.

[@GeneralistDev]

What is the extension name which maek comments fire and terminal icons

[@sandeepkumar-eq8nn]

Marunga mein he aur bachaunga bhi mein he

[@kuldeepvm]

You forgot to mention where that readResolve method is coming from.

[@nsudhir_here]

I am not a java person but I can guess that it comes from serializable interface.

[@kuldeepvm]

@@nsudhir_here nope. It's a marker interface.

[@siddharthdandamudi6949]

second point of Deserilization was confusing could have explained it better.

[@sagardarade]

With Deserialization Serialzation you did not explain how it's breaking singleton pattern.