Okay, let’s get into our topic. Today I will share with you the facade pattern# in the design pattern. ##. Use appropriate life stories and real project scenarios to tell the design pattern, and finally use one sentence to summarize this design pattern.

Story All development friends know that back-end development is usually:

controller---servie---dao/mapper/repository

However, I have asked many people whether they are familiar with the facade mode? Some people have been working for five years and don’t even know.

Overview of Facade Pattern Facade Pattern (Facade Pattern

English:

Provide a unified interface to a set of interfaces in asubsystem.Facade defines a higher-level interface that makes thesubsystem easier to use.

In fact, in daily coding work, we They are all using the facade pattern a lot, intentionally or unintentionally. Whenever a high-level module needs to schedule multiple subsystems (more than two class objects), we will consciously create a new class to encapsulate these subsystems and provide a streamlined interface so that high-level modules can more easily indirectly call the functions of these subsystems.

Cases in life

There are so many cases in life about the facade model.

Case 1: Go to the bank to handle business, and a front desk will receive you. Then, the front desk will ask you what business you need to do, and he will take you through it one by one, so that we don’t need to wander around and go everywhere. Find the corresponding business window. This front desk staff is equivalent to the facade model.

Case 2: When we build a house, if there is no contractor, you will have to find cement workers, electricians, decorators, etc. by yourself. But if you have a contractor, you don't have to do any of these tasks. You can tell the contractor directly that you need an electrician to fix the wiring. This contractor can be understood as a facade model.

Case 3: The controller developed by our backend can also be understood as a facade mode. For example, to obtain user account information, first check UserService to obtain user information, and then Check UserAccountService user account information.

Applicable scenarios for facade mode

In software systems, facade mode is suitable for the following application scenarios.

• Provide a simple interface for external access to a complex module or subsystem.
• When you want to improve the independence of the subsystem.
• When a subsystem may have bugs or performance-related problems due to unavoidable temporary reasons, a high-level interface can be provided through the facade mode to isolate the direct interaction between the client and the subsystem. Prevent code pollution.

General writing method of facade mode

Still use code to implement a simple facade mode , because what we like most is to start with the demo.

Business scenario: Now we need to call the respective methods of the three services:

public class ServiceA {
    public void doA(){
        System.out.println("do ServiceA");
    }
}
public class ServiceB {
    public void doB(){
        System.out.println("do ServiceB");
    }
}

public class ServiceC {
    public void doC(){
        System.out.println("do ServiceC");
    }
}

When the facade mode is not introduced, the client calls it like this:

public class Client {
    public static void main(String[] args) {
        ServiceA serviceA=new ServiceA();
        ServiceB serviceB=new ServiceB();
        ServiceC serviceC=new ServiceC();

        serviceA.doA();
        serviceB.doB();
        serviceC.doC();
    }
}

Every Secondly, the client itself needs to create many service objects. If there are many services involved, wouldn't this code be very embarrassing? There will be a lot of repetitive code.

Run result

do ServiceA
do ServiceB
do ServiceC

Let’s add Facade mode:

public class Facade {
    //是不是很像我們controller里注入各種service?
    private ServiceA serviceA = new ServiceA();
    private ServiceB serviceB = new ServiceB();
    private ServiceC serviceC = new ServiceC();

    public void doA() {
        serviceA.doA();
    }

    public void doB() {
        serviceB.doB();
    }

    public void doC() {
        serviceC.doC();
    }
}

The client becomes:

public class Client {
    public static void main(String[] args) {
        //輕輕松松的搞定，只需要創(chuàng)建門面這個對象即可
        Facade facade=new Facade();
        facade.doA();
        facade.doB();
        facade.doC();
    }
}

Run Result:

do ServiceA
do ServiceB
do ServiceC

Facade pattern UML diagram

Roles in Facade Mode

• Appearance role (Facade): Also called the facade role, it is the unified external interface of the system.
• Subsystem role (Service): There can be one or more Service at the same time. Each Service is not a separate class, but a collection of classes. Service do not know the existence of Facade. To the Service, Facade is just another client (that is, Facade is ServiceA, ServiceB, ServiceC transparent).

Extension of the facade pattern

Advantages

● Reduce system interdependence Think about it, if we don't use the facade mode, external access goes directly into the subsystem, and there is a strong coupling relationship between them. If you die, I will die, and if you live, I will live. Such strong dependence is the result of system design. Unacceptable, the emergence of the facade pattern solves this problem very well. All dependencies are on the facade objects and have nothing to do with the subsystem.

● Increased flexibility Dependence is reduced and flexibility is naturally increased. No matter how the subsystem changes internally, as long as it does not affect the facade object, you can move freely.

● 提高安全性 　　想讓你訪問子系統(tǒng)的哪些業(yè)務(wù)就開通哪些邏輯，不在門面上開通的方法，你休想訪問到 。

缺點

• 當(dāng)增加子系統(tǒng)和擴(kuò)展子系統(tǒng)行為時，可能容易帶來未知風(fēng)險。
• 不符合開閉原則。
• 某些情況下，可能違背單一職責(zé)原則。

大神們是如何使用的

在Spring中也是有大量使用到門面模式，比如說

org.springframework.jdbc.support.JdbcUtils

再來看看其中的方法

public static void closeConnection(@Nullable Connection con) {
    con.close();
}
public static Object extractDatabaseMetaData(DataSource dataSource, DatabaseMetaDataCallback action)
   throws MetaDataAccessException {
    Connection con = null;
  try {
   con = DataSourceUtils.getConnection(dataSource);
   DatabaseMetaData metaData = con.getMetaData();
   if (metaData == null) {
      //.....
   }
   return action.processMetaData(metaData);
  }
}
......

都是給我封裝好了方法，對于我們開發(fā)者來說，我只面向JdbcUtils這一個類就好了，我不用去管Connection、ResultSet等是怎么創(chuàng)建的，需要的時候，我調(diào)用JdbcUtils的對應(yīng)方法即可獲得對應(yīng)的對象。

在Mybatis中也是用到了門面模式，比如：

org.apache.ibatis.session.Configuration

在Configuration中以new開頭的方法，比如：

public Executor newExecutor(Transaction transaction) {
    return newExecutor(transaction, defaultExecutorType);
}
public MetaObject newMetaObject(Object object) {
    return MetaObject.forObject(object, objectFactory, objectWrapperFactory, reflectorFactory);
}

public ParameterHandler newParameterHandler(MappedStatement mappedStatement, Object parameterObject, BoundSql boundSql) {
    ...
    return parameterHandler;
}

public ResultSetHandler newResultSetHandler(Executor executor, MappedStatement mappedStatement, RowBounds rowBounds, ParameterHandler parameterHandler,
      ResultHandler resultHandler, BoundSql boundSql) {
   ...
    return resultSetHandler;
}

public StatementHandler newStatementHandler(Executor executor, MappedStatement mappedStatement）{
   ...
}

對于調(diào)用這些方法的地方，他并不知道是怎么new出來的對象，只管使用就行了。

在Tomcat中也有門面模式，比如：

org.apache.catalina.connector.RequestFacade

從名字就知道它用了門面模式。它封裝了非常多的request操作，也整合了很多servlet-api以外的內(nèi)容，給用戶使用提供了很大便捷。同樣，Tomcat針對Response和Session也封裝了對應(yīng)的ResponseFacade類和StandardSessionFacade類，感興趣的小伙伴可以深入了解一下。

PS：基本上所有以Facade結(jié)尾的類，都是使用到了門面模式。

Reference: Tom’s Design Pattern Course

Summary

Okay, I have shared so much about the facade mode. After reading this article, do you think that the facade mode is actually very simple? In addition, you can also consider whether it can be used at work. At the same time, it can also be used to brag during interviews.