I'm often faced with the problem of storing, in memory, a few (possibly complex) configuration settings loaded from files on the filesystem. I'm wondering if there's a better way to architect a pattern to this problem, however, than what I've been using.

Essentially, my current solution involves three steps.

1. Build a singleton. Since data is persistent and guaranteed not to change through the runtime of the application, only one object instance should ever be needed.
2. When the first request for the object is made, create the object and read in from a file.
3. Expose data with getters.

This has the effect that a lot of my code looks like this: 
`MyConfiguration.getInstance().getWeightOfBomb()`, which looks rather odd to me.

Is there a better way to handle this in a more semantic fashion?