Choosing Between HTTP/API/RPC Approaches in Effect Typescript Library
is there any sort of decision tree or line of thinking for when to use which http/api/rpc approaches provided?
i'm trying to read the docs and look at open source apps that use effect/platform for their api's, and it feels a bit hard to follow with the various options.
it seems i could:
- use
- use effect/rpc alongside schemas
- use HttpRouter standalone
there's just a lot of options in the general space of "make an api", i'm a bit confused on
(also, with the HttpApi api, is there a way to do a catch all route? HttpRouter has a
i'm trying to read the docs and look at open source apps that use effect/platform for their api's, and it feels a bit hard to follow with the various options.
it seems i could:
- use
HttpApiHttpApiBuilder- use effect/rpc alongside schemas
- use HttpRouter standalone
there's just a lot of options in the general space of "make an api", i'm a bit confused on
(also, with the HttpApi api, is there a way to do a catch all route? HttpRouter has a
.all
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
