Hi, many of us must have landed into a situation which I faced recently, the issue was with one of the new features deployed to PRODUCTION environment in the latest release not working as expected, but I was unable to reproduce this on Local or QA environments. So to debug it quickly, I tried something which ultimately proves really...
We often use synchronization. Imagine you have a use case in which there is some resource upon which writing is not done as much as compared to reading. So multiple threads should be able to read concurrently same resource without any problems. But if a single thread wants to write to the resource, for that all new threads for reading...