Why MyBatis Rules China While JPA Wins Abroad: A Deep Technical Comparison

1. Introduction

The discussion about SQL versus ORM never ends; this article presents an unbiased comparison of MyBatis and JPA without declaring a winner.

2. Current Ecosystem

According to the 2018 JVM ecosystem report, MyBatis accounts for only about 6% of usage worldwide. Google Trends shows that MyBatis interest is concentrated in China, Japan, and South Korea.

Another trend chart highlights the regional distribution of MyBatis users.

A third image shows that MyBatis popularity is mainly in East Asia.

3. Why Chinese Developers Prefer MyBatis

Big‑company influence: Many large Chinese internet firms copied Alibaba’s early use of iBatis/MyBatis, creating a talent pool familiar with it.

Low learning curve: Small companies need entry‑level programmers; MyBatis is easy to pick up.

Flexibility for simple projects: Most domestic projects are table‑centric, making MyBatis a convenient choice for CRUD‑heavy workloads.

Political/leadership demands: Projects often cater to managerial reporting needs, favoring quick SQL‑based solutions.

Hibernate/JPA learning cost: Although Spring Data JPA is simple, debugging and advanced features are cumbersome, discouraging adoption.

4. Why Foreign Teams Favor JPA

Legacy perception: Many overseas developers still think of MyBatis as iBatis.

Object‑oriented focus: JPA encourages domain‑driven design, keeping developers away from raw SQL.

DDD and long‑term stability: Complex business logic and long project lifespans benefit from JPA’s modeling capabilities.

Technology inertia: Teams often stick with well‑known frameworks like Spring.

Data volume: International projects usually handle smaller datasets, prioritizing stability over raw performance.

5. Personal Reflections

When applying DDD, MyBatis feels cumbersome, whereas JPA/Hibernate fits better. However, JPA/Hibernate requires a knowledgeable “hold” person; using a subset of its features or alternatives like EBean ORM can mitigate complexity.

6. Side‑by‑Side Comparison

The following images present a multi‑dimensional comparison of the two frameworks.

7. Conclusion

The choice between MyBatis and JPA depends on project size, team expertise, and architectural goals; both have strengths and trade‑offs.