|
| 1 | +--- |
| 2 | +layout: pattern |
| 3 | +title: Facade |
| 4 | +folder: facade |
| 5 | +permalink: /patterns/facade/ |
| 6 | +categories: Structural |
| 7 | +tags: |
| 8 | + - Gang Of Four |
| 9 | + - Decoupling |
| 10 | +--- |
| 11 | + |
| 12 | +## 目的 |
| 13 | +为一个子系统中的一系列接口提供一个统一的接口。外观定义了一个更高级别的接口以便子系统更容易使用。 |
| 14 | + |
| 15 | +## 解释 |
| 16 | + |
| 17 | +真实世界的例子 |
| 18 | + |
| 19 | +> 一个金矿是怎么工作的?“嗯,矿工下去然后挖金子!”你说。这是你所相信的因为你在使用一个金矿对外提供的一个简单接口,在内部它要却要做很多事情。这个简单的接口对复杂的子系统来说就是一个外观。 |
| 20 | +
|
| 21 | +用通俗的话说 |
| 22 | + |
| 23 | +> 外观模式为一个复杂的子系统提供一个简单的接口。 |
| 24 | +
|
| 25 | +维基百科说 |
| 26 | + |
| 27 | +> 外观是为很大体量的代码(比如类库)提供简单接口的一种对象。 |
| 28 | +
|
| 29 | +**程序示例** |
| 30 | + |
| 31 | +使用上面金矿的例子。这里我们有矮人的矿工等级制度。 |
| 32 | + |
| 33 | +```java |
| 34 | +public abstract class DwarvenMineWorker { |
| 35 | + |
| 36 | + private static final Logger LOGGER = LoggerFactory.getLogger(DwarvenMineWorker.class); |
| 37 | + |
| 38 | + public void goToSleep() { |
| 39 | + LOGGER.info("{} goes to sleep.", name()); |
| 40 | + } |
| 41 | + |
| 42 | + public void wakeUp() { |
| 43 | + LOGGER.info("{} wakes up.", name()); |
| 44 | + } |
| 45 | + |
| 46 | + public void goHome() { |
| 47 | + LOGGER.info("{} goes home.", name()); |
| 48 | + } |
| 49 | + |
| 50 | + public void goToMine() { |
| 51 | + LOGGER.info("{} goes to the mine.", name()); |
| 52 | + } |
| 53 | + |
| 54 | + private void action(Action action) { |
| 55 | + switch (action) { |
| 56 | + case GO_TO_SLEEP: |
| 57 | + goToSleep(); |
| 58 | + break; |
| 59 | + case WAKE_UP: |
| 60 | + wakeUp(); |
| 61 | + break; |
| 62 | + case GO_HOME: |
| 63 | + goHome(); |
| 64 | + break; |
| 65 | + case GO_TO_MINE: |
| 66 | + goToMine(); |
| 67 | + break; |
| 68 | + case WORK: |
| 69 | + work(); |
| 70 | + break; |
| 71 | + default: |
| 72 | + LOGGER.info("Undefined action"); |
| 73 | + break; |
| 74 | + } |
| 75 | + } |
| 76 | + |
| 77 | + public void action(Action... actions) { |
| 78 | + Arrays.stream(actions).forEach(this::action); |
| 79 | + } |
| 80 | + |
| 81 | + public abstract void work(); |
| 82 | + |
| 83 | + public abstract String name(); |
| 84 | + |
| 85 | + enum Action { |
| 86 | + GO_TO_SLEEP, WAKE_UP, GO_HOME, GO_TO_MINE, WORK |
| 87 | + } |
| 88 | +} |
| 89 | + |
| 90 | +public class DwarvenTunnelDigger extends DwarvenMineWorker { |
| 91 | + |
| 92 | + private static final Logger LOGGER = LoggerFactory.getLogger(DwarvenTunnelDigger.class); |
| 93 | + |
| 94 | + @Override |
| 95 | + public void work() { |
| 96 | + LOGGER.info("{} creates another promising tunnel.", name()); |
| 97 | + } |
| 98 | + |
| 99 | + @Override |
| 100 | + public String name() { |
| 101 | + return "Dwarven tunnel digger"; |
| 102 | + } |
| 103 | +} |
| 104 | + |
| 105 | +public class DwarvenGoldDigger extends DwarvenMineWorker { |
| 106 | + |
| 107 | + private static final Logger LOGGER = LoggerFactory.getLogger(DwarvenGoldDigger.class); |
| 108 | + |
| 109 | + @Override |
| 110 | + public void work() { |
| 111 | + LOGGER.info("{} digs for gold.", name()); |
| 112 | + } |
| 113 | + |
| 114 | + @Override |
| 115 | + public String name() { |
| 116 | + return "Dwarf gold digger"; |
| 117 | + } |
| 118 | +} |
| 119 | + |
| 120 | +public class DwarvenCartOperator extends DwarvenMineWorker { |
| 121 | + |
| 122 | + private static final Logger LOGGER = LoggerFactory.getLogger(DwarvenCartOperator.class); |
| 123 | + |
| 124 | + @Override |
| 125 | + public void work() { |
| 126 | + LOGGER.info("{} moves gold chunks out of the mine.", name()); |
| 127 | + } |
| 128 | + |
| 129 | + @Override |
| 130 | + public String name() { |
| 131 | + return "Dwarf cart operator"; |
| 132 | + } |
| 133 | +} |
| 134 | + |
| 135 | +``` |
| 136 | + |
| 137 | +为了操纵所有这些矿工我们有了这个外观 |
| 138 | + |
| 139 | +```java |
| 140 | +public class DwarvenGoldmineFacade { |
| 141 | + |
| 142 | + private final List<DwarvenMineWorker> workers; |
| 143 | + |
| 144 | + public DwarvenGoldmineFacade() { |
| 145 | + workers = List.of( |
| 146 | + new DwarvenGoldDigger(), |
| 147 | + new DwarvenCartOperator(), |
| 148 | + new DwarvenTunnelDigger()); |
| 149 | + } |
| 150 | + |
| 151 | + public void startNewDay() { |
| 152 | + makeActions(workers, DwarvenMineWorker.Action.WAKE_UP, DwarvenMineWorker.Action.GO_TO_MINE); |
| 153 | + } |
| 154 | + |
| 155 | + public void digOutGold() { |
| 156 | + makeActions(workers, DwarvenMineWorker.Action.WORK); |
| 157 | + } |
| 158 | + |
| 159 | + public void endDay() { |
| 160 | + makeActions(workers, DwarvenMineWorker.Action.GO_HOME, DwarvenMineWorker.Action.GO_TO_SLEEP); |
| 161 | + } |
| 162 | + |
| 163 | + private static void makeActions(Collection<DwarvenMineWorker> workers, |
| 164 | + DwarvenMineWorker.Action... actions) { |
| 165 | + workers.forEach(worker -> worker.action(actions)); |
| 166 | + } |
| 167 | +} |
| 168 | +``` |
| 169 | + |
| 170 | +现在来使用外观 |
| 171 | + |
| 172 | +```java |
| 173 | +DwarvenGoldmineFacade facade = new DwarvenGoldmineFacade(); |
| 174 | +facade.startNewDay(); |
| 175 | +// Dwarf gold digger wakes up. |
| 176 | +// Dwarf gold digger goes to the mine. |
| 177 | +// Dwarf cart operator wakes up. |
| 178 | +// Dwarf cart operator goes to the mine. |
| 179 | +// Dwarven tunnel digger wakes up. |
| 180 | +// Dwarven tunnel digger goes to the mine. |
| 181 | +facade.digOutGold(); |
| 182 | +// Dwarf gold digger digs for gold. |
| 183 | +// Dwarf cart operator moves gold chunks out of the mine. |
| 184 | +// Dwarven tunnel digger creates another promising tunnel. |
| 185 | +facade.endDay(); |
| 186 | +// Dwarf gold digger goes home. |
| 187 | +// Dwarf gold digger goes to sleep. |
| 188 | +// Dwarf cart operator goes home. |
| 189 | +// Dwarf cart operator goes to sleep. |
| 190 | +// Dwarven tunnel digger goes home. |
| 191 | +// Dwarven tunnel digger goes to sleep. |
| 192 | +``` |
| 193 | + |
| 194 | +## 类图 |
| 195 | + |
| 196 | + |
| 197 | +## 适用性 |
| 198 | +使用外观模式当 |
| 199 | + |
| 200 | +* 你想为一个复杂的子系统提供一个简单的接口。随着子系统的发展,它们通常会变得更加复杂。多数模式在应用时会导致更多和更少的类。这使子系统更可重用,更易于自定义,但是对于不需要自定义它的客户来说,使用它也变得更加困难。 外观可以提供子系统的简单默认视图,足以满足大多数客户端的需求。只有需要更多可定制性的客户才需要查看外观外的东西(原子系统提供的接口)。 |
| 201 | +* 客户端与抽象的实现类之间存在许多依赖关系。 引入外观以使子系统与客户端和其他子系统分离,从而提高子系统的独立性和可移植性。 |
| 202 | +* 您想对子系统进行分层。 使用外观来定义每个子系统级别的入口点。 如果子系统是相关的,则可以通过使子系统仅通过其外观相互通信来简化它们之间的依赖性。 |
| 203 | + |
| 204 | +## 鸣谢 |
| 205 | + |
| 206 | +* [Design Patterns: Elements of Reusable Object-Oriented Software](https://www.amazon.com/gp/product/0201633612/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0201633612&linkCode=as2&tag=javadesignpat-20&linkId=675d49790ce11db99d90bde47f1aeb59) |
| 207 | +* [Head First Design Patterns: A Brain-Friendly Guide](https://www.amazon.com/gp/product/0596007124/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0596007124&linkCode=as2&tag=javadesignpat-20&linkId=6b8b6eea86021af6c8e3cd3fc382cb5b) |
0 commit comments