单例设计模式
饿汉式、懒汉式(加锁,影响性能)、第三种方式都可以解决线程安全问题
Concept
A particular class should have only one instance. We will use only that instance whenever we are in need
饿汉式:
public class Singleton {
//必须是private修饰,不然其它类可以通过Singleton.singleton来获取Singleton实例
private static Singleton singleton = new Singleton();
//必须是private修饰,不然其它类可以通过new Singleton()来获取Singleton实例
private Singleton(){
}
//必须是public,用于其它类获取Singleton实例
public static Singleton getInstance(){
return singleton;
}
}
饿汉式在多线程情况下不会创建多个Singleton实例
懒汉式:
public class Singleton {
//必须是private修饰,不然其它类可以通过Singleton.singleton来获取Singleton实例
private static Singleton singleton = null;
//必须是private修饰,不然其它类可以通过new Singleton()来获取Singleton实例
private Singleton(){
}
//必须是public,用于其它类获取Singleton实例
public static Singleton getInstance(){
if(singleton==null){
singleton = new Singleton();
}
return singleton;
}
}
懒汉式有个问题,就是多线程情况下,会同时创建多个Singleton实例,所有多线程情况下必须加锁:
public static Singleton getInstance(){
synchronized (Singleton.class) {
if(singleton==null){
singleton = new Singleton();
}
}
return singleton;
}
对上面的代码可以优化,执行速度更快
public static Singleton getInstance(){
if (singleton == null) { //加个判断,这样不用所有的线程都进入同步代码块
synchronized (Singleton.class) {
if(singleton==null){
singleton = new Singleton();
}
}
}
return singleton;
}
测试:
@Test
public void test(){
Singleton s1 = Singleton.getInstance();
Singleton s2 = Singleton.getInstance();
System.out.println(s1==s2);
}
结果: true
**两种方式因为构造方法被private修饰,所以不能被继承**
第三种方式(推荐)
This method does not need to use the synchronization technique and eager initialization. It is regarded as the standard method to implement singletons in Java.
public class Singleton {
private static Singleton singleton = null;
private Singleton(){ }
/* 此处使用一个内部类来维护单例 */
private static class SingletonFactory {
private static Singleton instance = new Singleton();
}
public static Singleton getInstance(){
return SingletonFactory.instance;
}
}