ThinkerQAQ

NOTE

MyBatis Source Architecture

MyBatis execution flow from mapper proxy through mapped statement, executor, statement handler, parameter/result handling, and caching.

JavaCreated Updated 1 min readhistorical

This is a historical learning note and may contain outdated or incomplete understanding.

A useful MyBatis source-level model is:

  1. a mapper proxy turns an interface method into a mapped-statement invocation;
  2. SqlSession delegates execution to an Executor;
  3. statement/parameter handlers prepare JDBC SQL and bind parameters;
  4. JDBC executes the statement;
  5. result-set handling maps rows into Java results;
  6. cache/transaction behavior surrounds the execution path as configured.

Plugin interceptors wrap selected extension points and therefore can affect correctness/performance globally.

Exact classes/methods vary by version. Depend on public extension contracts and pin source analysis to the MyBatis release actually used.