effect-rpc-cluster

Build type-safe Effect RPC endpoints by defining shared Rpc and RpcGroup schemas with payload, success, and error contracts, then wiring RpcServer and RpcClient transport layers to reuse those exact definitions across client and server.

Set up sharded cluster entities in Effect by creating Entity definitions with sharded routing and durable request identity via Rpc primaryKey semantics, ensuring persistence dedupe across distributed cluster nodes.

Effect RPC supports streaming responses over WebSocket by defining Rpc values with optional stream support and mounting RpcServer transport layers configured with transport-specific layerProtocol and RpcSerialization settings.

Enforce validation middleware on Effect RPC servers by applying RpcMiddleware to handle cross-cutting concerns like token validation from request headers, including client-side enforcement using layerClient for wire-safe error schemas.

Effect cluster APIs support cron-driven singletons and durable workflow-style engines by defining Singleton entities and leveraging WorkflowProxy for client/server bridging under the effect/unstable/cluster package.

Effect RPC handlers fail with mismatched signatures when handler signatures are not aligned with the defined Rpc schemas, requiring correct Rpc primaryKey semantics and strict adherence to the effect/unstable/rpc API contracts.