Which has better activity and maintenance signals?

Based on the RepoPilot analysis, netflix/hystrix has significantly weaker maintenance signals than snailclimb/guide-rpc-framework.

netflix/hystrix: The verdict is explicitly "WAIT — Slowing — last commit 5mo ago". The README confirms Hystrix is in maintenance mode, not active development [netflix/hystrix README.md:L10-L21]. Netflix states: "Netflix will no longer actively review issues, merge pull-requests, and release new versions of Hystrix." The final release was 1.5.18, aligned with internal version 1.5.11 [netflix/hystrix README.md:L15-L16]. Hystrix is stable but no longer receiving active updates.

snailclimb/guide-rpc-framework: While the RepoPilot analysis for this repo wasn't included in the signals provided, the repository data shows it maintains multiple active components: service registration/discovery with Zookeeper integration, multiple serialization methods (Kryo, Protostuff, Hessian), load balancing strategies, Spring integration, and heartbeat detection [snailclimb/guide-rpc-framework README.md:L27-L39]. The environment requirements list current tools (JDK 25+, Maven 3.9+, Zookeeper 3.9.5+) [snailclimb/guide-rpc-framework README-EN.md:L93-L99], suggesting ongoing maintenance.

Summary: snailclimb/guide-rpc-framework appears more actively maintained, while netflix/hystrix is explicitly in long-term maintenance mode with no planned future development.

FOLLOW_UPS:

• What are Hystrix's core fault tolerance patterns and mechanisms?
• How does guide-rpc-framework implement service discovery?
• What's the purpose of Hystrix's metrics streaming architecture?