Home/ Questions/Q 5958241
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T18:30:53+00:00

I have a requirement to lazy-load resources in a concurrent environment. The code to

  • 0

I have a requirement to lazy-load resources in a concurrent environment. The code to load the resources should be executed only once.

Both Double-checked locking (using JRE 5+ and the volatile keyword) and Initialization on demand holder idiom seems to fit the job well.

Just by looking at the code, Initialization on demand holder idiom seems cleaner and more efficient (but hey, I’m guessing here). Still, I will have to take care and document the pattern at every one of my Singletons. At least to me, It would be hard to understand why code was written like this on the spot…

My question here is: Which approach s is better? And why?
If your answer is none. How would you tackle this requirement in a Java SE environment?

Alternatives

Could I use CDI for this without imposing it’s use over my entire project? Any articles out there?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    To add another, perhaps cleaner, option. I suggest the enum variation:

    What is the best approach for using an Enum as a singleton in Java?

    • 0