reactor-netty

Build reactive HTTP, TCP, and UDP servers and clients with Reactor Netty builders.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ririnto/sinon --skill reactor-netty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reactor-netty
Source: https://github.com/ririnto/sinon/tree/main/plugins/netty/skills/reactor-netty
Command: npx skills add https://github.com/ririnto/sinon --skill reactor-netty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reactor Netty provides a robust foundation for building reactive HTTP, TCP, and UDP servers and clients in Java without diving into low-level Netty internals.

Core Features & Use Cases

  • Reactive server/client construction: choose HttpServer, TcpServer, or UdpServer and compose inbound/outbound flows with non-blocking handlers.
  • Lifecycle and resource management: leverage hooks like doOnBind, doOnBound, and onDispose to manage startup, connection, and shutdown cleanly.
  • End-to-end flow without low-level Netty details: build around the common path builders and avoid direct channel/pipeline management.
  • TLS and observability options: enable TLS with secure(...), add wiretap, metrics, and access logging as needed.
  • Real-world usage: create a reactive HTTP server that binds, serves routes, and gracefully disposes.

Quick Start

Launch a simple HTTP server using Reactor Netty builders, bind it to a port, and shut it down gracefully.

Frequently Asked Questions about reactor-netty

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a reactive HTTP server without dealing with low-level Netty internals?

You can build a reactive HTTP server using Reactor Netty builders to compose inbound and outbound flows with non-blocking handlers, bypassing direct Netty channel and pipeline management. This provides an end-to-end reactive data flow without low-level complexity.

What lifecycle hooks are available for managing startup and shutdown in a reactive TCP server?

Reactor Netty provides lifecycle hooks like `doOnBind`, `doOnBound`, and `onDispose` for managing reactive TCP server startup, connection establishment, and graceful shutdown. These hooks ensure clean resource management throughout the server lifecycle.

Can I enable TLS and observability features for my reactive UDP server?

Yes, you can enable TLS on your reactive UDP server using the `secure(...)` builder method, and add observability features like wiretap, metrics, and access logging as needed. This secures and monitors your non-blocking UDP connections.

What's the best way to achieve end-to-end non-blocking I/O for network clients?

The best way to achieve end-to-end non-blocking I/O is by using Reactor Netty to construct reactive HTTP, TCP, or UDP clients. You compose inbound and outbound data flows directly with reactive handlers, ensuring completely non-blocking network communication.

Does this approach to building reactive servers require direct channel or pipeline management?

No, building reactive servers with Reactor Netty avoids direct channel and pipeline management. You use common path builders to construct servers and clients, allowing you to focus on reactive data flows rather than low-level Netty configurations.