It's well known one of the best ways to implement a singleton is to use `Enum`, made popular by [Josh Bloch](http://www.informit.com/articles/article.aspx?p=1216151&seqNum=3).

He states:

> 
> This approach is functionally equivalent to the public field approach, except that it is more concise, provides the serialization machinery for free, and provides an ironclad guarantee against multiple instantiation, even in the face of sophisticated serialization or reflection attacks. While this approach has yet to be widely adopted, **a single-element enum type is the best way to implement a singleton.**
> 
> 
> 

Does this still apply to a multi-element `Enum`? Won't each element be instantiated exactly once?

The perceived benefit would be to have several similar-but-different singleton-enum's, for example: each element injects a different configuration.

Example:

```
public enum Beatles {

    george("George"),
    john("John"),
    paul("Paul"),
    ringo("Ringo"),
    ;

    private Beatles(final String name) {
        this.name = name;
    }
    private final String name;

    public String getName() {
        return name;
    }
}

```