© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Clarification on Replacing tRPC with `HttpApi` or `Rpc` in Effect Typescript Library - Effect Community
EC
Effect Community
•
9mo ago
•
1 reply
Izak Filmalter
Clarification on Replacing tRPC with `HttpApi` or `Rpc` in Effect Typescript Library
I think I get it now
. If you are trying to replace tRPC in your app
, and you want to keep using REST
, use
HttpApi
HttpApi
, don
't use
Rpc
Rpc
. If you are wanting to switch off of REST to web sockets or support lots of transports
, maybe internal web sockets with external REST Api
, use
Rpc
Rpc
. Guess naming things is hard
.
In summary
, if you are trying to switch off of tRPC for your app
, just use
HttpApi
HttpApi
.
Using a custom runtime with `toWebHandler` and sharing a cache across requests can be a bit trick...
Effect Community
Join
Production-grade applications in TypeScript.
6,221
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Similar Threads
Was this page helpful?
Yes
No
Recent Announcements
Similar Threads
Difference Between `HttpApi` and `@effect/rpc` in Effect Typescript
EC
Effect Community / rpc
13mo ago
Defining RPC Handlers with Effect Typescript Library
EC
Effect Community / rpc
11mo ago
Accessing HttpServerRequest from within an RPC in Effect Typescript library
EC
Effect Community / rpc
9mo ago
Struggling with RpcServer Implementation in @effect/rpc Library
EC
Effect Community / rpc
13mo ago