effect-rpc-server

Build handlers with RpcGroup.toLayer or toLayerHandler, then pass the group to RpcServer.layer along with a protocol layer like layerProtocolHttp and a serialization layer like layerNdjson. Serve it through HttpRouter.serve with NodeHttpServer for a full Node setup.

Use layerNdjson or layerMsgPack for framed formats that support streaming responses over HTTP and raw TCP sockets. Plain layerJson only works over WebSocket or buffered HTTP, since it cannot split a byte stream into messages.

Define an RpcMiddleware.Service with an error schema and optional provides services, then implement it as a Layer whose function wraps the handler effect. Attach it per-rpc or to the whole group, and provide the layer to RpcServer.layer.

Yes, stream: true rpcs return a Stream or Queue and the server batches values into Chunk messages. Backpressure via client Ack messages works on WebSocket, TCP, stdio, and worker transports, but not on plain HTTP.

Use RpcTest.makeClient to create an in-process client wired to your handler and middleware layers with no transport. For single handlers, group.accessHandler resolves one handler with its captured services for direct unit testing.

On scope close the server rejects new messages, interrupts in-flight handler fibers, and flushes each final Exit before sending ClientEnd per client. Handlers wrapped in Rpc.uninterruptible run to completion even through shutdown.