effect-rpc-server

Build handlers with RpcGroup.toLayer or toLayerHandler, then compose them with RpcServer.layer, a protocol layer such as layerProtocolHttp, and one RpcSerialization layer. Serve the result through HttpRouter.serve with a NodeHttpServer layer.

Use WebSocket, TCP socket, stdio, or worker transports for streaming because they support acknowledgments that enable backpressure. Plain HTTP never throttles the producer, and only framed serializations like NDJSON or SchemaBinary emit response chunks incrementally.

No, in Effect v4 everything ships from the effect package under effect/unstable/rpc. There is no @effect/rpc package, so import RpcServer, RpcGroup, RpcMiddleware, and RpcSerialization directly from effect/unstable/rpc.

Define a service with RpcMiddleware.Service declaring an error schema and any provided context, 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.

By default a handler defect is treated as a protocol-level fault that fails all in-flight requests on the connection. Set disableFatalDefects to true in RpcServer.layer options so the defect is delivered only as that single request's Exit.

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