What are the migration paths between them?

I need to clarify your question. Based on the repository data, liyifeng1994/ssm and mybatis/mybatis-3 have different purposes:

• liyifeng1994/ssm is an educational tutorial project demonstrating SSM framework integration (SpringMVC + Spring + MyBatis) for beginners. It's a complete application example with controllers, services, DAOs, and tests.

• mybatis/mybatis-3 is the MyBatis core framework itself—a mature, actively maintained ORM library that provides the foundational data-mapping functionality.

These aren't alternatives to migrate between; rather, liyifeng1994/ssm depends on mybatis/mybatis-3. The ssm project uses MyBatis as its data access layer component.

Architectural relationship:

In liyifeng1994/ssm, you can see MyBatis usage in the DAO layer. For example, [src/main/java/com/soecode/lyf/dao/AppointmentDao.java:L7-L28] defines mapper interfaces with @Param annotations (a MyBatis feature) for parameter binding in SQL queries.

If you meant something else:

• Upgrading MyBatis versions within ssm? (updating the mybatis-3 dependency)
• Modernizing ssm itself? (The README notes the project is stale—last commit 3 years ago—and suggests moving to Spring Boot/Spring Cloud)
• Comparing MyBatis features across versions?

Could you clarify what kind of migration path you're asking about?

---

FOLLOW_UPS:

• How does ssm configure MyBatis through Spring integration?
• What mapper features does AppointmentDao demonstrate?
• Is ssm still maintained or deprecated?