// the take
A lightweight Java RPC framework from the same author as xxl-job, built on Netty with pluggable serialization (Hessian2, Kryo, Protostuff, JSONB) and load balancing strategies, plus a built-in service registry. It's aimed at teams that want Dubbo-style service-to-service calls without pulling in Dubbo or Zookeeper.
Clean layering between invoker, provider, registry, and transport means you can swap serializers or load-balancing strategies without touching call sites. It doesn't require Spring at all — can be started from a bare main() method, which is handy for quick service-to-service prototyping. Supports sync, oneway, future, and callback call types out of the box, which covers more invocation patterns than most minimal RPC libs bother with. Netty for transport means you're not relying on a homegrown I/O layer for the hot path.
668 stars for an RPC framework is a thin adoption signal next to Dubbo or gRPC — you'd be betting on a niche project for infrastructure-critical plumbing. Documentation is Chinese-only (the README itself says so), which is a real barrier if your team doesn't read Chinese and something breaks at 2am. The codebase has a large `util/old` package still shipping legacy Mina/Jetty/Servlet transports and old serializers alongside the current Netty path — that's dead weight carried for backward compat, and it's unclear which paths are actually maintained versus frozen. Service monitoring is explicitly listed as 'planned' in the feature list, meaning you don't get call-level observability without building it yourself, which matters a lot once this is running in production and something starts timing out.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →