effect-atom-rpc

Define a class extending AtomRpc.Service with your RpcGroup and a protocol layer such as RpcClient.layerProtocolHttp. The class exposes static query and mutation methods that return cached atoms consumable via useAtomValue and useAtomSet from @effect/atom-react.

Pass reactivityKeys to both the query and the mutation call. After a mutation succeeds, it fires Reactivity.invalidate with those keys, causing every query atom declaring overlapping keys to re-fetch automatically.

Yes, non-stream query atoms become serializable when you pass a stable serializationKey, keyed as AtomRpc:tag:key. Dehydrate the registry on the server with Hydration.dehydrate and call Hydration.hydrate on the client before rendering.

Yes, stream RPCs return an Atom.Writable of PullResult instead of AsyncResult. Write void to the atom to pull the next chunk, but note that stream queries cannot be serialized or hydrated.

AtomRpc targets RpcGroup definitions while AtomHttpApi targets HttpApi endpoints, but both expose the same query and mutation pattern. AtomHttpApi queries take group and endpoint names plus a request object instead of a tag and payload.

The mutation likely omitted reactivityKeys, so no query atoms were invalidated. Add reactivityKeys matching the keys declared on the affected queries, and avoid overly broad keys that invalidate unrelated data.