# tang-jie/NettyRPC

NettyRPC is high performance java rpc server base on Netty,using kryo,hessian,protostuff support message serialization.

Repository: https://github.com/tang-jie/NettyRPC
Canonical: https://ross.abutalabs.com/products/tang-jie-nettyrpc
Language: Java
License: NOASSERTION
License Family: other
Topics: netty, rpc, jmx, parallel, spring
Last push: 2018-02-02T03:43:57+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3688, "days_push": 3134, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1285, forks 503 (observed 2026-08-28T04:04:14.652150+00:00)

## What it is
NettyRPC is a high-performance Java RPC framework built on the Netty networking library, supporting multiple serialization codecs including JDK native, Kryo, Hessian, and Protostuff. It uses a master-slave Reactor thread model for parallel throughput, integrates with Spring for service lifecycle management, and provides JMX monitoring, async callbacks, and a web-based service interface viewer.

## Use cases
- build a high-performance RPC server in Java
- replace slow HTTP-based service calls with binary RPC
- serialize RPC messages with kryo, hessian, or protostuff
- manage RPC service registration and lifecycle through Spring
- monitor RPC server health via JMX
- handle long-running RPC calls with async callbacks
- expose service interface documentation over HTTP

## When to choose
- you need a lightweight, self-contained Java RPC framework without heavy middleware dependencies
- your stack already uses Spring and Netty
- you want pluggable serialization codecs for performance tuning
- you need fine-grained control over server thread pool behavior and task rejection policies

## When to avoid
- you need cross-language RPC (gRPC, Thrift) or polyglot service meshes
- you want built-in service discovery, load balancing, or distributed tracing out of the box
- you need a framework with active community support and frequent releases
- your team prefers standardized protocols over custom binary codecs

## Facets
- artifact type: framework
- maturity: maintenance
- function: rpc, serialization, middleware, monitoring, concurrency
- domain: microservices, backend, developer-tools
- platform: jvm
- tags: netty, kryo, hessian, protostuff, jmx, reactor-pattern, thread-pool, async-callback, service-discovery, high-performance, spring

## Member repositories
- tang-jie/NettyRPC (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:14.652150+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:56:41.439054+00:00, confidence not recorded.
  - readme: https://github.com/tang-jie/NettyRPC (fetched 2026-08-28T04:04:14.652150+00:00, sha 841b2be5a8b9)
- Data as of 2026-08-30T08:39:29.467469+00:00.