What are the migration paths between them?

I can only answer questions about mybatis/mybatis-3 or snailclimb/guide-rpc-framework.

These are two distinct projects with different purposes and no documented migration paths between them:

1. mybatis/mybatis-3 — A SQL mapper framework for Java that simplifies database access by coupling objects with SQL statements via XML or annotations. It's a mature ORM/data-access layer tool.

2. snailclimb/guide-rpc-framework — An RPC (Remote Procedure Call) framework built on Netty and Zookeeper for distributed service communication, featuring service registration, discovery, load balancing, and serialization.

Why no migration path exists:

• They solve different problems (data access vs. distributed RPC)
• MyBatis is production-ready at [20444 stars, 12861 forks] with strong maintenance signals
• guide-rpc-framework is an educational project designed for learning RPC architecture
• MyBatis handles SQL execution; guide-rpc-framework handles network service invocation

If your question is about integrating these tools (e.g., using MyBatis for database queries within an RPC service provider), that's a different architecture question I can help with. Or if you're asking about something specific within one of these repos, please clarify.

FOLLOW_UPS:

• How does MyBatis handle SQL parameter binding?
• What serialization methods does guide-rpc-framework support?
• How does guide-rpc-framework implement service discovery?