diff --git a/code/Java/design-pattern/EnumSingletonFile b/code/Java/design-pattern/EnumSingletonFile
new file mode 100644
index 0000000..a484639
Binary files /dev/null and b/code/Java/design-pattern/EnumSingletonFile differ
diff --git a/code/Java/design-pattern/SingletonFile b/code/Java/design-pattern/SingletonFile
new file mode 100644
index 0000000..3eb9713
Binary files /dev/null and b/code/Java/design-pattern/SingletonFile differ
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/simple_factory/PhoneFactory.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/simple_factory/PhoneFactory.java
index a17deb0..bafa319 100644
--- a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/simple_factory/PhoneFactory.java
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/simple_factory/PhoneFactory.java
@@ -14,15 +14,10 @@ public class PhoneFactory {
 	public Phone getPhone(Class<? extends Phone> phoneClass) {
 		try {
 			return (Phone) Class.forName(phoneClass.getName()).newInstance();
-		} catch (InstantiationException e) {
-			e.printStackTrace();
-		} catch (IllegalAccessException e) {
-			e.printStackTrace();
-		} catch (ClassNotFoundException e) {
+		} catch (InstantiationException | IllegalAccessException | ClassNotFoundException e) {
 			e.printStackTrace();
 		}
 		return null;
 	}
 
-
 }
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/DoubleCheckLazySingletonSafe.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/DoubleCheckLazySingletonSafe.java
new file mode 100644
index 0000000..d946b41
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/DoubleCheckLazySingletonSafe.java
@@ -0,0 +1,23 @@
+package com.heibaiying.creational.singleton;
+
+/**
+ * 使用双重检查锁来保证线程安全
+ */
+public class DoubleCheckLazySingletonSafe {
+
+	private static volatile DoubleCheckLazySingletonSafe instance = null;
+
+	private DoubleCheckLazySingletonSafe() {
+	}
+
+	public static DoubleCheckLazySingletonSafe getInstance() {
+		if (instance == null) {
+			synchronized (DoubleCheckLazySingletonSafe.class) {
+				if (instance == null) {
+					instance = new DoubleCheckLazySingletonSafe();
+				}
+			}
+		}
+		return instance;
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstance.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstance.java
new file mode 100644
index 0000000..b023c31
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstance.java
@@ -0,0 +1,23 @@
+package com.heibaiying.creational.singleton;
+
+/**
+ * 利用枚举实现单例
+ */
+public enum EnumInstance {
+
+	INSTANCE;
+
+	private String field;
+
+	public String getField() {
+		return field;
+	}
+
+	public void setField(String field) {
+		this.field = field;
+	}
+
+	public static EnumInstance getInstance() {
+		return INSTANCE;
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstanceTest.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstanceTest.java
new file mode 100644
index 0000000..601cff1
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/EnumInstanceTest.java
@@ -0,0 +1,21 @@
+package com.heibaiying.creational.singleton;
+
+import java.io.*;
+import java.lang.reflect.Constructor;
+
+public class EnumInstanceTest {
+	public static void main(String[] args) throws Exception {
+		// 序列化攻击
+		EnumInstance instance = EnumInstance.getInstance();
+		ObjectOutputStream outputStream = new ObjectOutputStream(new FileOutputStream("EnumSingletonFile"));
+		outputStream.writeObject(instance);
+		ObjectInputStream inputStream = new ObjectInputStream(new FileInputStream(new File("EnumSingletonFile")));
+		EnumInstance newInstance = (EnumInstance) inputStream.readObject();
+		System.out.println(instance == newInstance);
+		// 反射攻击，Enum类中只有一个两个参数的构造器：Enum(String name, int ordinal)
+		Constructor<EnumInstance> constructor = EnumInstance.class.getDeclaredConstructor(String.class, int.class);
+		constructor.setAccessible(true);
+		EnumInstance enumInstance = constructor.newInstance("name", 0);
+		System.out.println(instance == enumInstance);
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/HungrySingleton.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/HungrySingleton.java
new file mode 100644
index 0000000..146357c
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/HungrySingleton.java
@@ -0,0 +1,29 @@
+package com.heibaiying.creational.singleton;
+
+import java.io.Serializable;
+
+/**
+ * 利用静态代码块来实现饿汉式单例
+ */
+public class HungrySingleton implements Serializable {
+
+	private static final HungrySingleton instance;
+
+	static {
+		instance = new HungrySingleton();
+	}
+
+	private HungrySingleton() {
+		if (instance != null) {
+			throw new RuntimeException("单例模式禁止反射调用");
+		}
+	}
+
+	public static HungrySingleton getInstance() {
+		return instance;
+	}
+
+	private Object readResolve() {
+		return instance;
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/LazySingletonUnsafe.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/LazySingletonUnsafe.java
new file mode 100644
index 0000000..31710bb
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/LazySingletonUnsafe.java
@@ -0,0 +1,19 @@
+package com.heibaiying.creational.singleton;
+
+/**
+ * 线程不安全的懒汉式单例模式
+ */
+public class LazySingletonUnsafe {
+
+	private static LazySingletonUnsafe instance = null;
+
+	private LazySingletonUnsafe() {
+	}
+
+	public static LazySingletonUnsafe getInstance() {
+		if (instance == null) {
+			instance = new LazySingletonUnsafe();
+		}
+		return instance;
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ReflectionDamage.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ReflectionDamage.java
new file mode 100644
index 0000000..6e06fed
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ReflectionDamage.java
@@ -0,0 +1,15 @@
+package com.heibaiying.creational.singleton;
+
+import java.lang.reflect.Constructor;
+
+/**
+ * 利用反射破坏单例
+ */
+public class ReflectionDamage {
+	public static void main(String[] args) throws Exception {
+		Constructor<HungrySingleton> constructor = HungrySingleton.class.getDeclaredConstructor();
+		constructor.setAccessible(true);
+		HungrySingleton hungrySingleton = constructor.newInstance();
+		System.out.println(hungrySingleton);
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/SerializationDamage.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/SerializationDamage.java
new file mode 100644
index 0000000..78af91f
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/SerializationDamage.java
@@ -0,0 +1,17 @@
+package com.heibaiying.creational.singleton;
+
+import java.io.*;
+
+/**
+ * 利用序列化破坏单例
+ */
+public class SerializationDamage {
+	public static void main(String[] args) throws IOException, ClassNotFoundException {
+		HungrySingleton instance = HungrySingleton.getInstance();
+		ObjectOutputStream outputStream = new ObjectOutputStream(new FileOutputStream("SingletonFile"));
+		outputStream.writeObject(instance);
+		ObjectInputStream inputStream = new ObjectInputStream(new FileInputStream(new File("SingletonFile")));
+		HungrySingleton newInstance = (HungrySingleton) inputStream.readObject();
+		System.out.println(instance == newInstance);
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/StaticInnerClassHungrySingleton.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/StaticInnerClassHungrySingleton.java
new file mode 100644
index 0000000..eb56612
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/StaticInnerClassHungrySingleton.java
@@ -0,0 +1,21 @@
+package com.heibaiying.creational.singleton;
+
+/**
+ * 利用静态内部类来实现饿汉式单例
+ */
+public class StaticInnerClassHungrySingleton {
+
+	private static class InnerClass {
+		private static StaticInnerClassHungrySingleton instance = new StaticInnerClassHungrySingleton();
+	}
+
+	public static StaticInnerClassHungrySingleton getInstance() {
+		return InnerClass.instance;
+	}
+
+	private StaticInnerClassHungrySingleton() {
+		if (InnerClass.instance != null) {
+			throw new RuntimeException("单例模式禁止反射调用");
+		}
+	}
+}
diff --git a/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ZTest.java b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ZTest.java
new file mode 100644
index 0000000..b1e5378
--- /dev/null
+++ b/code/Java/design-pattern/src/main/java/com/heibaiying/creational/singleton/ZTest.java
@@ -0,0 +1,10 @@
+package com.heibaiying.creational.singleton;
+
+public class ZTest {
+	public static void main(String[] args) {
+		HungrySingleton hungrySingleton = HungrySingleton.getInstance();
+		StaticInnerClassHungrySingleton staticInnerClassHungrySingleton = StaticInnerClassHungrySingleton.getInstance();
+		DoubleCheckLazySingletonSafe doubleCheckLazySingletonSafe = DoubleCheckLazySingletonSafe.getInstance();
+		EnumInstance instance = EnumInstance.getInstance();
+	}
+}
diff --git a/notes/Java_设计模式.md b/notes/Java_设计模式.md
index 4f3d5db..526590e 100644
--- a/notes/Java_设计模式.md
+++ b/notes/Java_设计模式.md
@@ -2,38 +2,542 @@
 
 ## 软件设计的原则
 
-### 开闭原则
+### 1. 开闭原则
 
 定义：软件实体应当对扩展开放，对修改关闭。
 
-### 里氏替换原则
+### 2. 里氏替换原则
 
 定义：继承必须保证确保超类所拥有的性质在子类中仍然成立。即子类在继承父类时，除了添加新的方法来新增功能外，尽量避免重写父类方法，因为这会导致整个继承体系的复用性变差。
 
-### 依赖倒置原则
+### 3. 依赖倒置原则
 
 定义：高层模块不应该依赖低层模块，两者都应该依赖其抽象；抽象不应该依赖细节，细节应该依赖抽象。其核心思想是要面向接口编程，而不是面向实现编程，这样可以降低耦合性，提高系统稳定性，提高代码的可读性和可维护性。
 
-### 单一职责原则
+### 4. 单一职责原则
 
-定义：一个类应该有且仅有一个引起它变化的原则，否则应类应该被拆分。其核心思想是控制类的粒度大小、提高类的内聚性。
+定义：一个类应该有且仅有一个引起它变化的原则，否则类应该被拆分。其核心思想是控制类的粒度大小、提高类的内聚性。
 
-### 接口隔离原则
+### 5. 接口隔离原则
 
 定义：一个类对另一个类的依赖应该建立在最小的接口上。其核心思想是要为每个特定的功能建立对应的接口，而不是在一个接口中试图去包含所有功能，既要保证相对独立，也要避免过多接口所导致的臃肿。
 
-### 迪米特法则 (最少知道原则)
+### 6. 迪米特法则 (最少知道原则)
 
 定义：如果两个软件实体不需要直接通讯，那么就应该避免直接互相调用，而是通过第三方转发该调用，从而降低耦合度，保证模块的相对独立。
 
-### 合成复用原则 (组合复用原则)
+### 7. 合成复用原则 (组合复用原则)
 
 定义：应该优先使用组合、聚合等关联关系来实现复用，其次才是考虑使用继承关系。
 
-### 总结
+**总结**：开闭原则是总纲，它告诉我们要对扩展开放，对修改关闭；里氏替换原则告诉我们不要破坏继承体系；依赖倒置原则告诉我们要面向接口编程；单一职责原则告诉我们实现类要职责单一；接口隔离原则告诉我们在设计接口的时候要精简单一；迪米特法则告诉我们要降低耦合度；合成复用原则告诉我们要优先使用组合或者聚合关系复用，少用继承关系复用。
 
-开闭原则是总纲，它告诉我们要对扩展开放，对修改关闭；里氏替换原则告诉我们不要破坏继承体系；依赖倒置原则告诉我们要面向接口编程；单一职责原则告诉我们实现类要职责单一；接口隔离原则告诉我们在设计接口的时候要精简单一；迪米特法则告诉我们要降低耦合度；合成复用原则告诉我们要优先使用组合或者聚合关系复用，少用继承关系复用。
+# 创建型
 
+## 1. 单例模式
 
+### 1.1  饿汉式单例
 
-## 二、工厂模式
\ No newline at end of file
+饿汉式单例是最简单一种单例模式，它在类初始化时就完成相关单例对象的创建，可以通过静态代码块或静态内部类的方式来进行实现：
+
+静态代码块方式：
+
+```java
+public class HungrySingleton implements Serializable {
+
+	private static final HungrySingleton instance;
+
+	static {
+		instance = new HungrySingleton();
+	}
+
+    // 确保构造器私有
+	private HungrySingleton() {}
+
+    // 获取单例对象
+	public static HungrySingleton getInstance() {
+		return instance;
+	}
+}
+```
+
+静态内部类方式：
+
+```java
+public class StaticInnerClassHungrySingleton {
+
+	private static class InnerClass {
+		private static StaticInnerClassHungrySingleton instance = new StaticInnerClassHungrySingleton();
+	}
+
+     // 获取单例对象
+	public static StaticInnerClassHungrySingleton getInstance() {
+		return InnerClass.instance;
+	}
+    
+    // 确保构造器私有
+	private StaticInnerClassHungrySingleton() {
+	}
+}
+```
+
+恶汉式单例的优点在于其不存在线程安全问题，对象的唯一性由虚拟机在类初始化创建时保证；其缺点在于如果对象的创建比较消耗资源，并且单例对象不一定会被使用到，此时就会造成资源的浪费。
+
+### 1.2 懒汉式单例
+
+懒汉式单例的思想在于在需要使用单例对象时再进行创建，如果对象存在则直接返回，如果对象不存在则创建后返回，示例如下：
+
+```java
+public class LazySingletonUnsafe {
+
+	private static LazySingletonUnsafe instance = null;
+
+	private LazySingletonUnsafe() {
+	}
+
+	public static LazySingletonUnsafe getInstance() {
+		if (instance == null) {
+			instance = new LazySingletonUnsafe();
+		}
+		return instance;
+	}
+}
+```
+
+需要注意的是上面的代码在单线程环境下是没有问题的，但是在多线程环境下是线程不安全的，原因在于下面的创建代码是非原子性的：
+
+```java
+if (instance == null) {
+    instance = new LazySingletonUnsafe();
+}
+```
+
+想要保证创建操作的原子性，可以通过 synchronized 关键字来进行实现：
+
+```java
+public synchronized static LazySingletonUnsafe getInstance() {
+		if (instance == null) {
+			instance = new LazySingletonUnsafe();
+		}
+		return instance;
+	}
+```
+
+此时该方法是线程安全的，但是性能却存在问题。因为 synchronized 修饰的是静态方法，其锁住的是整个类对象，这意味着所有想要获取该单例对象的线程都必须要等待内部锁的释放。假设单例对象已经创建完成，并有 100 个线程并发获取该单例对象，则这 100 个线程都需要等待，显然这会降低系统的吞吐量，因此更好的方式是采用 **双重检查锁的机制** 来实现懒汉式单例：
+
+```java
+public class DoubleCheckLazySingletonSafe {
+
+    // 使用volatile来禁止指令重排序 
+    private static volatile DoubleCheckLazySingletonSafe instance = null;
+
+    private DoubleCheckLazySingletonSafe() {
+    }
+
+    public static DoubleCheckLazySingletonSafe getInstance() {
+        if (instance == null) {
+            synchronized (DoubleCheckLazySingletonSafe.class) {
+                if (instance == null) {
+                    instance = new DoubleCheckLazySingletonSafe();
+                }
+            }
+        }
+        return instance;
+    }
+}
+```
+
+还是沿用上面的举例，假设单例对象已经创建完成，并有 100 个线程并发获取该单例对象，此时 `instance == null` 判断肯定是 false，所以所有线程都会直接获得该单例对象，而不会进入 synchronized 同步代码块，这减小了锁的锁定范围，用更小的锁粒度获得了更好的性能。但内部的 `if` 代码块任然需要使用 synchronized 关键字修饰，从而保证整个 if 代码块的原子性。
+
+需要注意的是这里的 instance 需要使用 volatile 关键修饰，用于禁止对象在创建过程中出现指令重排序。通常对象的创建分为以下三步：
+
+1. 给对象分配内存空间；
+2. 调用对象的构造器方法，并执行初始化操作；
+3. 将变量指向相应的内存地址。
+
+如果没有禁止指令重排序，则 2 ，3 步可能会发生指令重排序，这在单线程下是没有问题的，也符合 As-If-Serial 原则，但是如果在多线程下就会出现线程不安全的问题：
+
+```java
+// 2. 由于线程1已经将变量指向内存地址，所以其他线程判断instance不为空，但instance可能尚未初始化完成
+if (instance == null) { 
+    synchronized (DoubleCheckLazySingletonSafe.class) {
+        if (instance == null) {
+            // 1. 假设线程1已经给对象分配了内存空间并将变量instance指向了相应的内存地址，但尚未初始化完成
+            instance = new DoubleCheckLazySingletonSafe();
+        }
+    }
+}
+return instance;
+```
+
+由于重排序的存在，其他线程可能拿到的是一个尚未初始化完成的 instance，此时就可能会导致异常，所以需要禁止其出现指令重排序。
+
+### 1.3  使用序列化破坏单例
+
+### 1.4 使用反射破坏单例
+
+### 1.5  枚举式单例
+
+## 2. 简单工厂模式
+
+### 2.1 定义
+
+对于调用者来说，它无需知道对象的具体创建细节，只需要将自己所需对象的类型告诉工厂，然后由工厂自动创建并返回。
+
+### 2.2 实现
+
+![23_simple_factory](../pictures/23_simple_factory.png)
+
+产品抽象类：
+
+```java
+public abstract class Phone {
+	public abstract void call(String phoneNum);
+}
+```
+
+具体的产品：
+
+```java
+public class HuaweiPhone extends Phone {
+    public void call(String phoneNum) {
+        System.out.println("华为手机拨打电话：" + phoneNum);
+    }
+}
+```
+
+```java
+public class XiaomiPhone extends Phone {
+    public void call(String phoneNum) {
+        System.out.println("小米手机拨打电话：" + phoneNum);
+    }
+}
+```
+
+手机工厂：
+
+```java
+public class PhoneFactory {
+
+    public Phone getPhone(String type) {
+        if ("xiaomi".equalsIgnoreCase(type)) {
+            return new XiaomiPhone();
+        } else if ("huawei".equalsIgnoreCase(type)) {
+            return new HuaweiPhone();
+        }
+        return null;
+    }
+}
+```
+
+调用工厂类获取具体的实例：
+
+```java
+public class ZTest {
+	public static void main(String[] args) {
+		PhoneFactory phoneFactory = new PhoneFactory();
+		phoneFactory.getPhone("xiaomi").call("123");
+		phoneFactory.getPhone("huawei").call("321");
+	}
+}
+```
+
+### 2.3  缺陷
+
+简单工厂的缺陷在于其违背了开闭原则。在简单工厂模式下，如果想要增加新的产品，就需要修改简单工厂中的判断逻辑，这就违背了开闭原则，因此其并不属于 GOF 经典的 23 种设计模式。在 Java 语言中，可以通过泛型来尽量规避这一缺陷，此时需要将创建产品的方法修改为如下所示：
+
+```java
+public Phone getPhone(Class<? extends Phone> phoneClass) {
+    try {
+        return (Phone) Class.forName(phoneClass.getName()).newInstance();
+    } catch (InstantiationException | IllegalAccessException | ClassNotFoundException e) {
+        e.printStackTrace();
+    }
+    return null;
+}
+```
+
+## 3. 工厂模式
+
+### 3.1  定义
+
+定义一个用于创建对象的工厂接口，但具体实例化哪一个工厂则由子类来决定。
+
+### 3.2 实现
+
+![23_factory_method](../pictures/23_factory_method.png)
+
+产品抽象类：
+
+```java
+public abstract class Phone {
+    public abstract void call(String phoneNum);
+}
+```
+
+产品实现类：
+
+```java
+public class HuaweiPhone extends Phone {
+    public void call(String phoneNum) {
+        System.out.println("华为手机拨打电话：" + phoneNum);
+    }
+}
+```
+
+```java
+public class XiaomiPhone extends Phone {
+    public void call(String phoneNum) {
+        System.out.println("小米手机拨打电话：" + phoneNum);
+    }
+}
+```
+
+工厂接口：
+
+```java
+public interface Factory {
+    Phone produce();
+}
+```
+
+工厂实现类：
+
+```java
+public class HuaweiPhoneFactory implements Factory {
+    @Override
+    public Phone produce() {
+        return new HuaweiPhone();
+    }
+}
+```
+
+```java
+public class XiaomiPhoneFactory implements Factory {
+    @Override
+    public Phone produce() {
+        return new XiaomiPhone();
+    }
+}
+```
+
+由调用者来决定实例化哪一个工厂对象：
+
+```java
+public class ZTest {
+    public static void main(String[] args) {
+        XiaomiPhoneFactory xiaomiPhoneFactory = new XiaomiPhoneFactory();
+        xiaomiPhoneFactory.produce().call("123");
+        HuaweiPhoneFactory huaweiPhoneFactory = new HuaweiPhoneFactory();
+        huaweiPhoneFactory.produce().call("456");
+    }
+}
+```
+
+## 4. 抽象工厂模式
+
+### 4.1  定义
+
+提供一个创建一系列相关或相互依赖对象的接口，而无需指定它们具体的实现类。
+
+### 4.2  实现
+
+![23_abstract_factory](../pictures/23_abstract_factory.png)
+
+假设工厂除了生产手机外，也生产手机的充电器，此时抽象工厂的示例如下：
+
+充电器抽象类：
+
+```java
+public abstract class Charger {
+    public abstract void Charge(Phone phone);
+}
+```
+
+充电器实现类：
+
+```java
+public class HuaiweiCharger extends Charger {
+    @Override
+    public void Charge(Phone phone) {
+        System.out.println("华为充电器给" + phone + "充电");
+    }
+}
+```
+
+```java
+public class XiaomiCharger extends Charger {
+    @Override
+    public void Charge(Phone phone) {
+        System.out.println("小米充电器给" + phone + "充电");
+    }
+}
+```
+
+工厂接口：
+
+```java
+public interface Factory {
+    Phone producePhone();
+    Charger produceCharger();
+}
+```
+
+工厂实现类：
+
+```java
+public class HuaweiPhoneFactory implements Factory {
+    @Override
+    public Phone producePhone() {
+        return new HuaweiPhone();
+    }
+    @Override
+    public Charger produceCharger() {
+        return new HuaiweiCharger();
+    }
+}
+```
+
+```java
+public class XiaomiPhoneFactory implements Factory {
+    @Override
+    public Phone producePhone() {
+        return new XiaomiPhone();
+    }
+    @Override
+    public Charger produceCharger() {
+        return new XiaomiCharger();
+    }
+}
+```
+
+调用具体的工厂实现类：
+
+```java
+public class ZTest {
+	public static void main(String[] args) {
+		XiaomiPhoneFactory xiaomiPhoneFactory = new XiaomiPhoneFactory();
+		xiaomiPhoneFactory.produceCharger().Charge(xiaomiPhoneFactory.producePhone());
+		HuaweiPhoneFactory huaweiPhoneFactory = new HuaweiPhoneFactory();
+		huaweiPhoneFactory.produceCharger().Charge(huaweiPhoneFactory.producePhone());
+	}
+}
+```
+
+## 5. 构建者模式
+
+### 5.1 定义
+
+将一个复杂对象的构造与它的表示分离，使同样的构建过程可以创建不同的表示。它是将一个复杂对象的创建过程分解为多个简单的步骤，然后一步一步的组装完成。
+
+### 5.2 示例
+
+![23_builder](../pictures/23_builder.png)
+
+产品实体类：
+
+```java
+public class Phone {
+	/*处理器*/
+	private String processor;
+	/*摄像头*/
+	private String camera;
+	/*屏幕*/
+	private String screen;
+}
+```
+
+建造者抽象类：
+
+```java
+public abstract class Builder {
+
+    protected Phone phone = new Phone();
+	/*安装处理器*/
+    public abstract void addProcessor();
+	/*组装摄像头*/
+    public abstract void addCamera();
+	/*安装屏幕*/
+    public abstract void addScreen();
+  
+    public Phone produce() {
+        return phone;
+    }
+}
+```
+
+建造者实现类：
+
+```java
+public class HuaweiBuilder extends Builder {
+    @Override
+    public void addProcessor() {
+        phone.setProcessor("海思麒麟处理器");
+    }
+
+    @Override
+    public void addCamera() {
+        phone.setCamera("莱卡摄像头");
+    }
+
+    @Override
+    public void addScreen() {
+        phone.setScreen("OLED");
+    }
+}
+```
+
+```java
+public class XiaomiBuilder extends Builder {
+	@Override
+	public void addProcessor() {
+		phone.setProcessor("高通骁龙处理器");
+	}
+
+	@Override
+	public void addCamera() {
+		phone.setCamera("索尼摄像头");
+	}
+
+	@Override
+	public void addScreen() {
+		phone.setScreen("OLED");
+	}
+}
+```
+
+定义管理者类：
+
+```java
+public class Manager {
+
+	private Builder builder;
+
+	public Manager(Builder builder) {
+		this.builder = builder;
+	}
+
+	public Phone buy() {
+		builder.addCamera();
+		builder.addProcessor();
+		builder.addScreen();
+		return builder.produce();
+	}
+}
+```
+
+调用管理者类获取产品：
+
+```java
+public class ZTest {
+	public static void main(String[] args) {
+		Phone huawei = new Manager(new HuaweiBuilder()).buy();
+		System.out.println(huawei);
+		Phone xiaomi = new Manager(new XiaomiBuilder()).buy();
+		System.out.println(xiaomi);
+	}
+}
+// 输出：
+Phone(processor=海思麒麟处理器, camera=莱卡摄像头, screen=OLED)
+Phone(processor=高通骁龙处理器, camera=索尼摄像头, screen=OLED)
+```
\ No newline at end of file
diff --git a/pictures/23_abstract_factory.png b/pictures/23_abstract_factory.png
new file mode 100644
index 0000000..a9959b9
Binary files /dev/null and b/pictures/23_abstract_factory.png differ
diff --git a/pictures/23_builder.png b/pictures/23_builder.png
new file mode 100644
index 0000000..64c0659
Binary files /dev/null and b/pictures/23_builder.png differ
diff --git a/pictures/23_factory_method.png b/pictures/23_factory_method.png
new file mode 100644
index 0000000..23f36cd
Binary files /dev/null and b/pictures/23_factory_method.png differ
diff --git a/pictures/23_simple_factory.png b/pictures/23_simple_factory.png
new file mode 100644
index 0000000..9cbe187
Binary files /dev/null and b/pictures/23_simple_factory.png differ