Mybatis分层架构

Mybatis主要分为三层，接口层负责提供数据的增删改查接口、数据处理层则负责具体SQL的执行、框架层则提供Mybatis的底层配置，如数据源、具体sql、事务等配置
image.png

Mybatis的请求处理过程

Mysql执行请求主要是通过SqlSession来进行的，SqlSession作为最顶层的接口，提供增删改查，内部交给Executor去执行（其有几个不同的实现类，分别用来处理不同的查询以及一级和二级缓存）
9033085-ca3974e212f792a0.webp

Mybatis的缓存设计

Mybatis支持一级缓存和二级缓存。
一级缓存默认是会话级别的，也可以通过在Configuration中配置，来设置为statement级别。

  1. <setting name="localCacheScope" value="SESSION"/>

二级缓存则可以跨会话，是NameSpace级别的，二级缓存需要在Configuration开启Cache，并在需要缓存的NameSpace下配置Cache标签

  1. //config.xml中开启二级缓存
  2. <setting name="cacheEnabled" value="true"/>
  3. //xxxMapper.xml中配置cache,默认是本地缓存，可以指定为其他外部缓存
  4. <cache/>

image.png

Mybatis源码知识脑图

Mybatis - 图4

SqlSessionFactory

SqlSessionFactory是Mybatis的SqlSession会话工厂，用来获得一个会话。前面我们已经看到所有的请求都是通过SqlSession进行处理的。当Mybatis与Spring整合时，其作为一个Bean是通过SqlSessionFactoryBean来实例化的，其内部主要通过SqlSessionFactoryBuilder来进行构造，build方法需要一个Configuration实例。其默认实现是DefaultSqlSessionFactory

  1. //SqlSessionFactoryBean  
  2. protected SqlSessionFactory buildSqlSessionFactory() throws IOException {
  4.     Configuration configuration;
  5.     //这里解析config.xml、xxxMapper.xml等配置文件得到Configuration实例
  6.     XMLConfigBuilder xmlConfigBuilder = null;
  7.     if (this.configLocation != null) {
  8.       xmlConfigBuilder = new XMLConfigBuilder(this.configLocation.getInputStream(), null, this.configurationProperties);
  9.       configuration = xmlConfigBuilder.getConfiguration();
  10.     } else {
  11.       if (logger.isDebugEnabled()) {
  12.         logger.debug("Property 'configLocation' not specified, using default MyBatis Configuration");
  13.       }
  14.       configuration = new Configuration();
  15.       configuration.setVariables(this.configurationProperties);
  16.     }
  18.     if (this.objectFactory != null) {
  19.       configuration.setObjectFactory(this.objectFactory);
  20.     }
  22.     if (this.objectWrapperFactory != null) {
  23.       configuration.setObjectWrapperFactory(this.objectWrapperFactory);
  24.     }
  26.     if (hasLength(this.typeAliasesPackage)) {
  27.       String[] typeAliasPackageArray = tokenizeToStringArray(this.typeAliasesPackage,
  28.           ConfigurableApplicationContext.CONFIG_LOCATION_DELIMITERS);
  29.       for (String packageToScan : typeAliasPackageArray) {
  30.         configuration.getTypeAliasRegistry().registerAliases(packageToScan,
  31.                 typeAliasesSuperType == null ? Object.class : typeAliasesSuperType);
  32.         if (logger.isDebugEnabled()) {
  33.           logger.debug("Scanned package: '" + packageToScan + "' for aliases");
  34.         }
  35.       }
  36.     }
  38.     if (!isEmpty(this.typeAliases)) {
  39.       for (Class<?> typeAlias : this.typeAliases) {
  40.         configuration.getTypeAliasRegistry().registerAlias(typeAlias);
  41.         if (logger.isDebugEnabled()) {
  42.           logger.debug("Registered type alias: '" + typeAlias + "'");
  43.         }
  44.       }
  45.     }
  47.     if (!isEmpty(this.plugins)) {
  48.       for (Interceptor plugin : this.plugins) {
  49.         configuration.addInterceptor(plugin);
  50.         if (logger.isDebugEnabled()) {
  51.           logger.debug("Registered plugin: '" + plugin + "'");
  52.         }
  53.       }
  54.     }
  56.     if (hasLength(this.typeHandlersPackage)) {
  57.       String[] typeHandlersPackageArray = tokenizeToStringArray(this.typeHandlersPackage,
  58.           ConfigurableApplicationContext.CONFIG_LOCATION_DELIMITERS);
  59.       for (String packageToScan : typeHandlersPackageArray) {
  60.         configuration.getTypeHandlerRegistry().register(packageToScan);
  61.         if (logger.isDebugEnabled()) {
  62.           logger.debug("Scanned package: '" + packageToScan + "' for type handlers");
  63.         }
  64.       }
  65.     }
  67.     if (!isEmpty(this.typeHandlers)) {
  68.       for (TypeHandler<?> typeHandler : this.typeHandlers) {
  69.         configuration.getTypeHandlerRegistry().register(typeHandler);
  70.         if (logger.isDebugEnabled()) {
  71.           logger.debug("Registered type handler: '" + typeHandler + "'");
  72.         }
  73.       }
  74.     }
  76.     if (xmlConfigBuilder != null) {
  77.       try {
  78.         xmlConfigBuilder.parse();
  80.         if (logger.isDebugEnabled()) {
  81.           logger.debug("Parsed configuration file: '" + this.configLocation + "'");
  82.         }
  83.       } catch (Exception ex) {
  84.         throw new NestedIOException("Failed to parse config resource: " + this.configLocation, ex);
  85.       } finally {
  86.         ErrorContext.instance().reset();
  87.       }
  88.     }
  90.     if (this.transactionFactory == null) {
  91.       this.transactionFactory = new SpringManagedTransactionFactory();
  92.     }
  94.     Environment environment = new Environment(this.environment, this.transactionFactory, this.dataSource);
  95.     configuration.setEnvironment(environment);
  97.     if (this.databaseIdProvider != null) {
  98.       try {
  99.         configuration.setDatabaseId(this.databaseIdProvider.getDatabaseId(this.dataSource));
  100.       } catch (SQLException e) {
  101.         throw new NestedIOException("Failed getting a databaseId", e);
  102.       }
  103.     }
  105.     //解析Bean中配置mapperLocation中指定的xml文件，与Spring集成后一般不会直接写在config.xml中
  106.     if (!isEmpty(this.mapperLocations)) {
  107.       for (Resource mapperLocation : this.mapperLocations) {
  108.         if (mapperLocation == null) {
  109.           continue;
  110.         }
  112.         try {
  113.           XMLMapperBuilder xmlMapperBuilder = new XMLMapperBuilder(mapperLocation.getInputStream(),
  114.               configuration, mapperLocation.toString(), configuration.getSqlFragments());
  115.           xmlMapperBuilder.parse();
  116.         } catch (Exception e) {
  117.           throw new NestedIOException("Failed to parse mapping resource: '" + mapperLocation + "'", e);
  118.         } finally {
  119.           ErrorContext.instance().reset();
  120.         }
  122.         if (logger.isDebugEnabled()) {
  123.           logger.debug("Parsed mapper file: '" + mapperLocation + "'");
  124.         }
  125.       }
  126.     } else {
  127.       if (logger.isDebugEnabled()) {
  128.         logger.debug("Property 'mapperLocations' was not specified or no matching resources found");
  129.       }
  130.     }
  132.     return this.sqlSessionFactoryBuilder.build(configuration);
  133.   }

Configuration

Configuration也是Mybatis一个非常核心的类，实例这个对象需要解析Mybatis的config.xml文件和所有的Mapper.xml文件，并为每个Statement建立一个缓存，还会为每个Mapper接口绑定一个MapperProxyFactory工厂。Configuration解析配置文件主要通过XmlConfigBuilder、XmlMapperBuilder、XmlStatementBuild来分别解析全局配置文件、Mapper配置文件和具体的Statement配置

SqlSession

SqlSession里面定义了增删改查的方法，其默认实现为DefaultSqlSession，通过SqlSessionFactory进行获取，下面主要看两个问题：
（1）Mapper接口的查询是如何被代理的
通常我们只需要定义查询的Dao接口，但不需要实现，而Mybatis是通过动态代理来实现的，具体可以查看DefaultSqlSession的getMapper方法

  1. //DefaultSqlSession
  2. public <T> T getMapper(Class<T> type) {
  3.     return configuration.<T>getMapper(type, this);
  4.   }
  5. //Configuration
  6. public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
  7.     return mapperRegistry.getMapper(type, sqlSession);
  8.   }
  9. //MapperRegistry
  10. public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
  11.     final MapperProxyFactory<T> mapperProxyFactory = (MapperProxyFactory<T>) knownMappers.get(type);
  12.     if (mapperProxyFactory == null)
  13.       throw new BindingException("Type " + type + " is not known to the MapperRegistry.");
  14.     try {
  15.       return mapperProxyFactory.newInstance(sqlSession);
  16.     } catch (Exception e) {
  17.       throw new BindingException("Error getting mapper instance. Cause: " + e, e);
  18.     }
  19.   }
  20. //MapperProxyFactory
  21. //这里使用了jdk的动态代理，为Mapper生成了一个代理类
  22. protected T newInstance(MapperProxy<T> mapperProxy) {
  23.     return (T) Proxy.newProxyInstance(mapperInterface.getClassLoader(), new Class[] { mapperInterface }, mapperProxy);
  24.   }
  26.   public T newInstance(SqlSession sqlSession) {
  27.     final MapperProxy<T> mapperProxy = new MapperProxy<T>(sqlSession, mapperInterface, methodCache);
  28.     return newInstance(mapperProxy);
  29.   }
  30. //MapperProxy
  31. //MapperProxy实现了InvocationHandler接口，来进行代理，一般的invoke方法都会调用被代理接口的实现类的具体方法，
  32. //但是Mybatis里实际上只有Mapper接口，这里并没有实现类，而是直接将请求交给了MapperMethod去处理了
  33. public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
  34.     if (Object.class.equals(method.getDeclaringClass())) {
  35.       try {
  36.         return method.invoke(this, args);
  37.       } catch (Throwable t) {
  38.         throw ExceptionUtil.unwrapThrowable(t);
  39.       }
  40.     }
  41.     final MapperMethod mapperMethod = cachedMapperMethod(method);
  42.     return mapperMethod.execute(sqlSession, args);
  43.   }
  45.   private MapperMethod cachedMapperMethod(Method method) {
  46.     MapperMethod mapperMethod = methodCache.get(method);
  47.     if (mapperMethod == null) {
  48.       mapperMethod = new MapperMethod(mapperInterface, method, sqlSession.getConfiguration());
  49.       methodCache.put(method, mapperMethod);
  50.     }
  51.     return mapperMethod;
  52.   }
  53. //MapperMethod, 可以看出最终内部是通过SqlSession对应的curd接口进行数据库的操作的
  54. public Object execute(SqlSession sqlSession, Object[] args) {
  55.     Object result;
  56.     if (SqlCommandType.INSERT == command.getType()) {
  57.       Object param = method.convertArgsToSqlCommandParam(args);
  58.       result = rowCountResult(sqlSession.insert(command.getName(), param));
  59.     } else if (SqlCommandType.UPDATE == command.getType()) {
  60.       Object param = method.convertArgsToSqlCommandParam(args);
  61.       result = rowCountResult(sqlSession.update(command.getName(), param));
  62.     } else if (SqlCommandType.DELETE == command.getType()) {
  63.       Object param = method.convertArgsToSqlCommandParam(args);
  64.       result = rowCountResult(sqlSession.delete(command.getName(), param));
  65.     } else if (SqlCommandType.SELECT == command.getType()) {
  66.       if (method.returnsVoid() && method.hasResultHandler()) {
  67.         executeWithResultHandler(sqlSession, args);
  68.         result = null;
  69.       } else if (method.returnsMany()) {
  70.         result = executeForMany(sqlSession, args);
  71.       } else if (method.returnsMap()) {
  72.         result = executeForMap(sqlSession, args);
  73.       } else {
  74.         Object param = method.convertArgsToSqlCommandParam(args);
  75.         result = sqlSession.selectOne(command.getName(), param);
  76.       }
  77.     } else {
  78.       throw new BindingException("Unknown execution method for: " + command.getName());
  79.     }
  80.     if (result == null && method.getReturnType().isPrimitive() && !method.returnsVoid()) {
  81.       throw new BindingException("Mapper method '" + command.getName() 
  82.           + " attempted to return null from a method with a primitive return type (" + method.getReturnType() + ").");
  83.     }
  84.     return result;
  85.   }

（2）SqlSession是如何执行Sql的
这里以selectOne为例，其内部会调用selectList，然后会交给Executor去执行，而具体使用哪个Executor是依据Sql类型来决定的，如果开启了二级缓存，还会用CachingExecutor对内部实际的Executor进行包装

  1. //DefaultSqlSession
  2. public <E> List<E> selectList(String statement, Object parameter, RowBounds rowBounds) {
  3.     try {
  4.       //从Configuration中拿到对应的Statement
  5.       MappedStatement ms = configuration.getMappedStatement(statement);
  6.       //调用executor的query
  7.       List<E> result = executor.query(ms, wrapCollection(parameter), rowBounds, Executor.NO_RESULT_HANDLER);
  8.       return result;
  9.     } catch (Exception e) {
  10.       throw ExceptionFactory.wrapException("Error querying database.  Cause: " + e, e);
  11.     } finally {
  12.       ErrorContext.instance().reset();
  13.     }
  14.   }
  16. //BaseExecutor
  17. public <E> List<E> query(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler) throws SQLException {
  18.     BoundSql boundSql = ms.getBoundSql(parameter);
  19.     CacheKey key = createCacheKey(ms, parameter, rowBounds, boundSql);
  20.     return query(ms, parameter, rowBounds, resultHandler, key, boundSql);
  21.  }
  22. public <E> List<E> query(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, CacheKey key, BoundSql boundSql) throws SQLException {
  23.     ErrorContext.instance().resource(ms.getResource()).activity("executing a query").object(ms.getId());
  24.     if (closed) throw new ExecutorException("Executor was closed.");
  25.     if (queryStack == 0 && ms.isFlushCacheRequired()) {
  26.       clearLocalCache();
  27.     }
  28.     List<E> list;
  29.     try {
  30.       queryStack++;
  31.       //这里有一个localCache，实际上就是一级缓存，内部是一个HashMap
  32.       list = resultHandler == null ? (List<E>) localCache.getObject(key) : null;
  33.       if (list != null) {
  34.         handleLocallyCachedOutputParameters(ms, key, parameter, boundSql);
  35.       } else {
  36.         list = queryFromDatabase(ms, parameter, rowBounds, resultHandler, key, boundSql);
  37.       }
  38.     } finally {
  39.       queryStack--;
  40.     }
  41.     if (queryStack == 0) {
  42.       for (DeferredLoad deferredLoad : deferredLoads) {
  43.         deferredLoad.load();
  44.       }
  45.       deferredLoads.clear(); // issue #601
  46.       if (configuration.getLocalCacheScope() == LocalCacheScope.STATEMENT) {
  47.         clearLocalCache(); // issue #482
  48.       }
  49.     }
  50.     return list;
  51.   }
  52. //查数据库
  53. private <E> List<E> queryFromDatabase(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, CacheKey key, BoundSql boundSql) throws SQLException {
  54.     List<E> list;
  55.     localCache.putObject(key, EXECUTION_PLACEHOLDER);
  56.     try {
  57.       //这里使用了模板方法设计模式，doQuery的逻辑交给BaseExecutor的子类去实现
  58.       list = doQuery(ms, parameter, rowBounds, resultHandler, boundSql);
  59.     } finally {
  60.       localCache.removeObject(key);
  61.     }
  62.     localCache.putObject(key, list);
  63.     if (ms.getStatementType() == StatementType.CALLABLE) {
  64.       localOutputParameterCache.putObject(key, parameter);
  65.     }
  66.     return list;
  67.   }
  68. //SimpleExecutor的实现
  69. public <E> List<E> doQuery(MappedStatement ms, Object parameter, RowBounds rowBounds, ResultHandler resultHandler, BoundSql boundSql) throws SQLException {
  70.     Statement stmt = null;
  71.     try {
  72.       Configuration configuration = ms.getConfiguration();
  73.       //
  74.       StatementHandler handler = configuration.newStatementHandler(wrapper, ms, parameter, rowBounds, resultHandler, boundSql);
  75.       stmt = prepareStatement(handler, ms.getStatementLog());
  76.       //调用StatementHandler的query方法去查询， 底层是基于jdbc的PreparedStatement、statement等来查询数据
  77.       return handler.<E>query(stmt, resultHandler);
  78.     } finally {
  79.       closeStatement(stmt);
  80.     }
  81.   }
  82. //这里以PreparedStatementHandler的实现，得到数据之后通过ResultSetHandler来处理返回值
  83. public <E> List<E> query(Statement statement, ResultHandler resultHandler) throws SQLException {
  84.     PreparedStatement ps = (PreparedStatement) statement;
  85.     ps.execute();
  86.     return resultSetHandler.<E> handleResultSets(ps);
  87.   }

Executor的实现类如下：
image.png
StatementHandler的实现类：
StatementHandler.png
Cache的实现类：里面的很多类都采用了装饰器模式，来装饰底层的cache

装饰链路：SynchronizedCache -> LoggingCache -> SerializedCache -> LruCache -> PerpetualCache。

Cache.png
其中LRUCache的实现是基于LinkedHashMap来实现的， 主要是重写其removeEldestEntry方法。如果是自己实现，可以基于HashMap + LinkedList来实现

  1. public class LruCache implements Cache {
  3.   private final Cache delegate;
  4.   private Map<Object, Object> keyMap;
  5.   private Object eldestKey;
  7.   public LruCache(Cache delegate) {
  8.     this.delegate = delegate;
  9.     setSize(1024);
  10.   }
  12.   @Override
  13.   public String getId() {
  14.     return delegate.getId();
  15.   }
  17.   @Override
  18.   public int getSize() {
  19.     return delegate.getSize();
  20.   }
  22.   public void setSize(final int size) {
  23.     keyMap = new LinkedHashMap<Object, Object>(size, .75F, true) {
  24.       private static final long serialVersionUID = 4267176411845948333L;
  26.       protected boolean removeEldestEntry(Map.Entry<Object, Object> eldest) {
  27.         boolean tooBig = size() > size;
  28.         if (tooBig) {
  29.           eldestKey = eldest.getKey();
  30.         }
  31.         return tooBig;
  32.       }
  33.     };
  34.   }
  36.   @Override
  37.   public void putObject(Object key, Object value) {
  38.     delegate.putObject(key, value);
  39.     cycleKeyList(key);
  40.   }
  42.   @Override
  43.   public Object getObject(Object key) {
  44.     keyMap.get(key); //touch
  45.     return delegate.getObject(key);
  46.   }
  48.   @Override
  49.   public Object removeObject(Object key) {
  50.     return delegate.removeObject(key);
  51.   }
  53.   @Override
  54.   public void clear() {
  55.     delegate.clear();
  56.     keyMap.clear();
  57.   }
  59.   public ReadWriteLock getReadWriteLock() {
  60.     return null;
  61.   }
  63.   private void cycleKeyList(Object key) {
  64.     keyMap.put(key, key);
  65.     if (eldestKey != null) {
  66.       delegate.removeObject(eldestKey);
  67.       eldestKey = null;
  68.     }
  69.   }

写在最后

Mybatis虽然解决Java对象和数据库之间的ORM映射，为开发省去了手写jdbc和事务等重复的逻辑。但目前的数据库架构早已告别了单机时代，而集群时代又将面临很多Mybatis所解决不了的问题，如更多的数据、更高的并发等，因而就衍生了支持读写分离和分库分表的更上层的数据访问层的中间件