Understanding HttpLayerRouter vs. HttpApiBuilder in Effect/HTTP Modules
Hi, I'm trying to implement an api with effect/http modules. I've hit a couple road bumps and working through it trying to use the type system to understand what to use/provide when
the one thing I don't follow, and for which I see some different approaches across different courses/example apps, is when to use HttpLayerRouter vs. HttpApiBuilder
It feels like these are two completely different approaches to putting together a router? but then I see samples that seem to combine the two eg. https://github.com/lucas-barake/building-an-app-with-effect/blob/main/packages/server/src/server.ts. is there rationale for what to use when? or am I misunderstanding entirely what each is built for
the one thing I don't follow, and for which I see some different approaches across different courses/example apps, is when to use HttpLayerRouter vs. HttpApiBuilder
It feels like these are two completely different approaches to putting together a router? but then I see samples that seem to combine the two eg. https://github.com/lucas-barake/building-an-app-with-effect/blob/main/packages/server/src/server.ts. is there rationale for what to use when? or am I misunderstanding entirely what each is built for
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
