What are the migration paths between them?

I can only answer questions about conductor-oss/conductor or snailclimb/guide-rpc-framework.

These are two distinct, independent projects with different purposes:

• conductor-oss/conductor is an event-driven agentic workflow engine for orchestrating microservices and AI agents at scale.
• snailclimb/guide-rpc-framework is an educational RPC framework implementation featuring Netty-based networking, service registry/discovery with Zookeeper, and multiple serialization methods.

They are not designed to interoperate, and there are no documented migration paths between them. They solve different problems:

• Conductor handles durable workflow orchestration and agent execution
• guide-rpc-framework provides low-level RPC communication primitives

If you have questions about migration within either project (e.g., upgrading Conductor versions or understanding guide-rpc-framework's architecture), I'm happy to help with those.

FOLLOW_UPS:

• How does Conductor's agent execution model work?
• What serialization methods does guide-rpc-framework support?
• How do Conductor workflows handle failure recovery?